[Bug 442475] New: The Cancel and Skip Refresh still does Not Operate with a Higher Priory than the Yast Application Itself

List overview All Threads
Download

newer

older

[Bug 469784] New: Nautilus :...

[Bug 476298] New: Creating an NTP...

bugzilla_noreply＠novell.com

6 Nov 2008 6 Nov '08

21:27

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(a)forge.provo.novell.com ReportedBy: alpha096(a)virginbroadband.com.au QAContact: jsrain(a)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.

Show replies by date

bugzilla_noreply＠novell.com

12 Nov 12 Nov

09:34

New subject: [Bug 442475] 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 User mseben(a)novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=442475#c1 Michal Seben <mseben(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mseben(a)novell.com Status|NEW |NEEDINFO Info Provider| |alpha096(a)virginbroadband.com.au --- Comment #1 from Michal Seben <mseben(a)novell.com> 2008-11-12 02:34:00 MST --- could you please specify in which cases this behaviour occurs ? e.g. i try this on opensuse 11.1 beta 4: i run yast software managment in search I enter "a" and i check all checkboxes (Name,Summary,Desctription ...etc) in "Search in" group then i press search, and while yast was searching it offer me "cancel button" and this button works well thanks -- 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.

bugzilla_noreply＠novell.com

20:50

New subject: [Bug 442475] The Cancel and Skip Refresh still does Not Operate with a Higher Priory than the Yast Application Itself

bugzilla_noreply＠novell.com

20:53

New subject: [Bug 442475] The Cancel and Skip Refresh still does Not Operate with a Higher Priory than the Yast Application Itself

bugzilla_noreply＠novell.com

13 Nov 13 Nov

23:21

New subject: [Bug 442475] 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 Robert Vojcik <rvojcik(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening(a)forge.provo.novell.com |yast2-maintainers(a)suse.de -- 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.

bugzilla_noreply＠novell.com

14 Nov 14 Nov

16:57

New subject: [Bug 442475] 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 User sh(a)novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=442475#c4 Stefan Hundhammer <sh(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |alpha096(a)virginbroadband.com.au --- Comment #4 from Stefan Hundhammer <sh(a)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.

bugzilla_noreply＠novell.com