If the activities are not asked to save when power is running out, then that is a bug. We should fix it.
On Tue, Jun 17, 2014 at 2:15 PM, Frederick Grose <fgr...@gmail.com> wrote: > On Tue, Jun 17, 2014 at 12:26 PM, Sebastian Silva < > sebast...@fuentelibre.org> wrote: > >> >> >> El mar, 17 de jun 2014 a las 5:45 AM, Sam Parkinson < >> sam.parkins...@gmail.com> escribió: >> >> For GTK activities they only seem to save (please correct me if I'm >> wrong) when you navigate away from the activity. This is annoying when >> your XO runs out of power and your still working on your assignment :) Is >> there any reason for this? >> >> Sam >> >> It used to be the case that there was a "keep" button for explicitly >> saving (a copy or I guess revision). however it was removed and yes, it's >> super counter-intuitive to have to change context to save your work. >> Perhaps we should make a bug to track the issue, even though it's about UI >> design? >> >> > > The design intent is described here: > > http://wiki.sugarlabs.org/go/Human_Interface_Guidelines/The_Laptop_Experience/The_Journal#The_Notion_of_.22Keeping.22 > > There is a link in that section where one can see some history on > discussion of the issue. > > Activity authors might program in saving rules that serve the purposes of > the Activity, such as, saving on a selected frequency for text editors. > > _______________________________________________ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > -- Walter Bender Sugar Labs http://www.sugarlabs.org
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
