[Bug 442475] New: The Cancel and Skip Refresh still does Not Operate with a Higher Priory than the Yast Application Itself
https://bugzilla.novell.com/show_bug.cgi?id=442475 Summary: The Cancel and Skip Refresh still does Not Operate with a Higher Priory than the Yast Application Itself Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: alpha096@virginbroadband.com.au QAContact: jsrain@novell.com Found By: Customer If a Yast Application stalls at any point, using the Cancel Button has NO effect on the Yast Application. There needs to have both Cancel and Skip Refresh and Abort buttons operate with a much higher Priority that the Yast Application itself. Using the 'Skip Refresh' button certainly does work most of the time but not 100% of the time - Its Priority still needs to be higher. The cancel or Abort buttons - never close or stop a misbehaving Yast Application or abouts the saving of a Yast Application and is essentially useless. Both Abort, Cancel and Skip Refresh, all need to operate with the Highest CPU authority or always higher than the Yast Application itself. 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 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=442475
User mseben@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=442475#c1
Michal Seben
https://bugzilla.novell.com/show_bug.cgi?id=442475
User alpha096@virginbroadband.com.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=442475#c2
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=442475
User alpha096@virginbroadband.com.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=442475#c3
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=442475
Robert Vojcik
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
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.
https://bugzilla.novell.com/show_bug.cgi?id=442475
User alpha096@virginbroadband.com.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=442475#c5
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=442475
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=442475#c6
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=442475
User alpha096@virginbroadband.com.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=442475#c7
--- Comment #7 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=442475
User alpha096@virginbroadband.com.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=442475#c8
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=442475
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=442475#c9
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=442475
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=442475#c10
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=442475
User alpha096@virginbroadband.com.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=442475#c11
--- Comment #11 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=442475
Stefan Hundhammer
https://bugzilla.novell.com/show_bug.cgi?id=442475
User mvidner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=442475#c12
Martin Vidner
https://bugzilla.novell.com/show_bug.cgi?id=442475
User alpha096@virginbroadband.com.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=442475#c13
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=442475
User jsmeix@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=442475#c14
Johannes Meixner
participants (1)
-
bugzilla_noreply@novell.com