UDC menu's Apply button

[zer0]

Code: Select all

v9.90.0515 - 2011-03-22 22:28
    * Manage User-Defined Commands Dialog: Re-added the buttons Apply
      and Reset to the Command Properties section. They had been removed
      in v8.80.0014 - 2010-01-09 16:12, but now I think it was a bad
      idea.

Over a year on and no complaints in the forum, so what is the reason the change of mind?

Yesterday I came back to actually using this interface and found it unintuitive.

Sorry, but could you please be a bit more specific? Unintuitive by itself sounds too vague. What happened to your assertions of consistency and removing the need for a user to confirm things over and over?

[admin]

Code: Select all

v9.90.0515 - 2011-03-22 22:28
    * Manage User-Defined Commands Dialog: Re-added the buttons Apply
      and Reset to the Command Properties section. They had been removed
      in v8.80.0014 - 2010-01-09 16:12, but now I think it was a bad
      idea.

Over a year on and no complaints in the forum, so what is the reason the change of mind?

Yesterday I came back to actually using this interface and found it unintuitive.

Sorry, but could you please be a bit more specific? Unintuitive by itself sounds too vague. What happened to your assertions of consistency and removing the need for a user to confirm things over and over?

I intuitively found it unintuitive. I have no time to analyze this, sorry.

[PeterH]

Code: Select all

v9.90.0515 - 2011-03-22 22:28
    * Manage User-Defined Commands Dialog: Re-added the buttons Apply
      and Reset to the Command Properties section. They had been removed
      in v8.80.0014 - 2010-01-09 16:12, but now I think it was a bad
      idea.

Over a year on and no complaints in the forum, so what is the reason the change of mind?

Yesterday I came back to actually using this interface and found it unintuitive.

Sorry, but could you please be a bit more specific? Unintuitive by itself sounds too vague. What happened to your assertions of consistency and removing the need for a user to confirm things over and over?

I intuitively found it unintuitive. I have no time to analyze this, sorry.

Just want to add my 2 cent...

I hope you know that this is strange from position of the customer?
Zero asked for a change, you didn't want.
Later you made the change. As a reason you say "Now I had to use this fuction, and found it unintuitive". At least this doesn't seem very good...

OK: I'm sure such things must happen from time to time...
In this case: bad experience and bad luck for zer0.
You might learn that sometimes(!) wishes of customers are better than they seem at a first look.

But nothing can help: you have to decide - and sometimes your decision will not be the best. (I'd say: thanks god!)

[admin]

I'm always trying to remove strangeness from the customer. But I sometimes change my mind about certain decisions. Intuition is an important resource for decisions, especially in UI design. Intuition is better after a certain time has passed. Else your thoughts get in the way. Coming back to the UDC dialog after more than year I found it strange and also buggy (when switching the category all changes were lost -- nobody reported this bug in one year).

Now I reread the thread, and made up my mind (again) about the confirmation dialog. Next version (v9.90.0518) will prompt you before changes are lost.

[zer0]

Now I reread the thread, and made up my mind (again) about the confirmation dialog. Next version (v9.90.0518) will prompt you before changes are lost.

Under what circumstances would changes be lost? Save for clicking "Cancel" in the overall UDC dialogue window, of course.

[admin]

Now I reread the thread, and made up my mind (again) about the confirmation dialog. Next version (v9.90.0518) will prompt you before changes are lost.

Under what circumstances would changes be lost? Save for clicking "Cancel" in the overall UDC dialogue window, of course.

When changing the Category or the Command without having pressed Apply.

[zer0]

When changing the Category or the Command without having pressed Apply.

So back to the old days, except with a confirmation pop-up?

I don't like this approach at all for the same reasons as already explained previously in this thread. Now, if I want to jump between a few scripts to copy/paste bits and pieces, I have to OK/Cancel a dialogue window? Sounds like fun that I could well do without. It certainly won't help me do my tasks any quicker. This nested complexity of having a confirmation (Apply/Reset) within a confirmation (OK/Cancel UDC dialogue) with additional confirmation (OK/Cancel the pop-up) is unnecessary and is over-the-top.

Why can't things be simple: saving changes on-the-fly when switching between commands/categories and "Cancel" in the UDC dialogue to discard them.

[Stefan]

I didn't read the whole thread (but i should i think)
but here is what i expect from such an dialog:

- i can edit all i want, nothing is saved yet
- i can even switch categories and no (temp till now) changes are lost
- if i close the dialog or press [cancel] all changes are dropped
- if i want to save my modifications i close the dialog by pressing [OK]
- if i want to save my change in between -before i try other things and maybe mess all up again- i would press [Apply]
( [Apply] is the same as pressing [OK] to save&close and open the dialog again )


But i had never an issue with the Manage UDC dialog, maybe i use it not heavy enough? ;-)

.

[admin]

Why can't things be simple: saving changes on-the-fly when switching between commands/categories and "Cancel" in the UDC dialogue to discard them.

I added a tweak to return to before v9.90.0515.

In the meantime I recognized that my problem came from the little asterisk showing that the properties are "dirty" (= need saving). This asterisk implies for me that active saving/applying is needed. I removed the asterisk and things are now better for me in the pre v9.90.0515 state.

UPDATE: I added ESC to reset dirty settings (without using Reset button), which makes the asterisk useful again... never mind.

[admin]

OK, I reviewed the auto-apply behavior after the recent changes and bug fixes, and now think it works. Which also means that I don't have to rewrite the documentation again.

[zer0]

OK, I reviewed the auto-apply behavior after the recent changes and bug fixes, and now think it works. Which also means that I don't have to rewrite the documentation again.

Nice one, good to know we could resolve it amicably