https://bugzilla.novell.com/show_bug.cgi?id=489077
User jsrain@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=489077#c2
Jiri Srain changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
CC| |jsrain@novell.com
Info Provider|jsrain@novell.com |
--- Comment #2 from Jiri Srain 2009-03-30 02:28:24 MDT ---
I'm not sure, which is the right solution. Looking at suggestions above:
a) is not a way to go; there are operations which can be interrupted at some
point (but not immediately); graying out such button would remove the chance of
interrupting such operations. If an operation cannot be interrupted at all,
graying out the button is an option, but this can only be done on per-case
basis.
b) can be done by the maintainers of individual UIs. If there already is some
change in the button representation (I have not noticed), it might be quite
simple
c) would work only if you know how much time an operation can take - and does
not solve operations which can be interrupted at some points. Flickerking
pop-ups are not a prefered way
d) better feedback may be an option, but don't know how to best represent being
busy
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.