Opened 9 years ago

Closed 6 years ago

#2151 closed enhancement (fixed)

Shutdown and Logout menu items should activate the busy cursor (or provide some other visual feedback)

Reported by: garycmartin Owned by: tomeu
Priority: Unspecified by Maintainer Milestone: Unspecified
Component: Sugar Version: Unspecified
Severity: Minor Keywords: sugar-love
Cc: smparrish Distribution/OS: Unspecified
Bug Status: Unconfirmed

Description (last modified by garycmartin)

Shutdown (and Logout) menu items should activate the busy cursor (or provide some other visual feedback, perhaps dimming/locking the UI from use). If you trigger these menu items with a number of activities resumed there can be a very long wait before anything visually happens, the user may well start to do other things, or hard power off. With 9 activities open on an XO-1, the time between selecting Shutdown from the central XO home icon and the display visual changing, was between 40sec and 70sec

Attachments (2)

Change History (12)

comment:1 Changed 9 years ago by anurag_seeta

  • Resolution set to fixed
  • Status changed from new to closed

r?

comment:2 Changed 9 years ago by seeta

Anurag, since we had posted the patch to sugar-devel. So r? not required in this case. r? required when we upload the patch at bug tracker.

comment:3 Changed 9 years ago by tomeu

  • Resolution fixed deleted
  • Status changed from closed to reopened

Please be very careful to not close tickets that are not really fixed yet.

comment:4 follow-up: Changed 9 years ago by anurag_seeta

The bug #2151 requires us to place any form of visual notification upon the start of code execution of the shutdown procedure so as to confirm of the start of the process. One of the suggested fixes being , to change the cursor to busy cursor and for that to happen we must change the behavior of the cursor to that of the busy cursor just after the call of the shutdown procedure function , so from online research and discussion at community at IRC channels I reached to the code snip "self.window.set_cursor( gtk.gdk.Cursor(gtk.gdk.WATCH) )" {Link: http://wiki.laptop.org/go/Sugar_almanac} for which i made and applied a patch , but the patch failed to work on Sugar jh-build and the current situation of the debugging of this bug states that the the code change line (quoted above) cannot bring about the required and expected change as it must apply the cursor change code at a higer level of access, (i.e. may be it requires some special privileges enabled to make the change allowable and reflectable ).

comment:5 in reply to: ↑ 4 Changed 9 years ago by tomeu

Replying to anurag_seeta:

The bug #2151 requires us to place any form of visual notification upon the start of code execution of the shutdown procedure so as to confirm of the start of the process. One of the suggested fixes being , to change the cursor to busy cursor and for that to happen we must change the behavior of the cursor to that of the busy cursor just after the call of the shutdown procedure function , so from online research and discussion at community at IRC channels I reached to the code snip "self.window.set_cursor( gtk.gdk.Cursor(gtk.gdk.WATCH) )" {Link: http://wiki.laptop.org/go/Sugar_almanac} for which i made and applied a patch , but the patch failed to work on Sugar jh-build and the current situation of the debugging of this bug states that the the code change line (quoted above) cannot bring about the required and expected change as it must apply the cursor change code at a higer level of access, (i.e. may be it requires some special privileges enabled to make the change allowable and reflectable ).

There are no privileges involved on this at all, see the mailing list thread for more information.

comment:6 Changed 9 years ago by garycmartin

  • Description modified (diff)
  • Summary changed from Shutdown and Logout menu items should activate the buzzy cursor (or provide some other visual feedback) to Shutdown and Logout menu items should activate the busy cursor (or provide some other visual feedback)

comment:7 Changed 9 years ago by smparrish

  • Cc smparrish added

comment:8 Changed 9 years ago by smparrish

  • seeta_dev set to Ishan, Anurag

comment:9 Changed 9 years ago by anurag_seeta

r?

comment:10 Changed 6 years ago by worr

  • Resolution set to fixed
  • Status changed from reopened to closed

This feature has since been added

Note: See TracTickets for help on using tickets.