Lost with "apply" buttons

[bodziak]

There is bug in Girder - the "apply" button. What I mean ?
1. You open hardware plugins section, then select plugin, press "apply " - but you still can't edit setings for newly seleted plugin. - strange!
2. You try to set new settings for plugin, a new popup window shows. You set new settings in this window the press apply- the settings are not saved until you press aplay i plugin window.
3. Let's say you are playing with volume settnigs. You set new increase volume action - the last selected action in remebered (ok) - then you create action for decrease volume then go to O.S. you see that all setting are shown, but "applay" button is inactive.

There is proposed solution for issue 3.
- Add tab with decription (text only of assinged action for command) so when you browse commnd in the you see in this tab description of action
- add flag (bit) in Girder source wchich is set to true if tab other than dectiption is clicked by user.
- if any element in command tree in cliked and flag is set to true then raise qusetion to "applay" or discard" settings

[Ron]

hi,

1. Girder uses this strange mechanism to conserve memory, it doesn't load all the plugins at startup, so you have to "select"
the plugin (the checkmark) press apply.
Now the plugin is loaded then select the plugin and press settings. The settings dialog popups.

2. It seems only logical to press the apply
on the popup dialog to save the settings of
the hardware plugin.

3.The Apply button is greyed out because as
far as girder is concerned you did not
type anything yet... allthough i agree that
the apply mechanism on these tabs sux :(

- Ron

[bodziak]

About point 1.
If Girder will work in this way it will be OK. But currently you must
- select plugin
- press applay
- press OK
- close settings window
- open settings window again
- press button to set plugin settings

[Yvonus]

Despite being unable to describe so precisely what I sometimes notice, I have to admit that I've taken the habit to click on any "apply" button that is around by fear of losing the command I'm just creating.

When capturing a system event, I select ok in the associated window, then I must not forget to press apply again to be sure that what I've just selected is taken into account.

So I guess I won't be against a less "risky" interface way of being sure I don't lose what I'm doing.