https://bugzilla.novell.com/show_bug.cgi?id=442475 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=442475#c4 Stefan Hundhammer <sh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |alpha096@virginbroadband.com.au --- Comment #4 from Stefan Hundhammer <sh@novell.com> 2008-11-14 09:57:36 MST --- (In reply to comment #0 from Scott Couston)
Both Abort, Cancel and Skip Refresh, all need to operate with the Highest CPU authority or always higher than the Yast Application itself.
Are you aware that you cannot assign priorities to individual widgets in the same program / process? Are you aware that you are greatly simplifying and generalizing things? You claim that "Cancel" buttons never work. That is certainly not true. There may be operations done in the foreground that sometimes take longer than desirable. Maybe some of those operations can be split up into sub-tasks so UI feedback can be maintained. But then, you are surely aware that there is no simple and generic way to do that everywhere. A global statement like "Cancel and Abort never work" does not make any sense, nor is there anything to pinpoint, anything to work on. It's very much like demanding "the world must become a better place". If you can identify situations and places in YaST where you can turn that general statement into anything concrete, let's hear it. But just that general statement alone will not do anybody any good.
We have taken for granted that both cancel or Abort buttons never function after we commit to any changes via a Yast Application Window and perhaps it is long overdue for us to correct this
Who is that "we" and "us" in that context? -- 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.