> From: Guilhem Bonnefille <guilhem.bonnefi...@gmail.com> > Subject: Re: [Viking-devel] Bug squashing for v1.0 > To: Greg Troxel <g...@ir.bbn.com> > >> ^S - save file associated with current window >> ^W - close current window, prompting if modified. >> exit if this is the last one. >> ^Q - close all windows and exit, prompting if modified > > You're right. I think, the motivation to diverge was that it is > particularly difficult to decide when a viking document is modified or > not. In other words, when the user considers that its document is > modified. For example, does the user expects to save its document when > it simply open and move viewport to left?
If you open a large text file with emacs and scroll down, it doesn't
modify the file. One of the things I really dislike about MS Office is
that looking at a file considers it modified. But, having a position
within the file remembered would seem to have some value.
> But I agree with Greg: we need to restore standard notions.
> The question is: what about detecting document modifications.
>
> I'm not sure it will be easy to implement something to detect changes.
>
> Any idea?
> Should we always open a dialog like « Do you want to save your work?
> Yes/No » at closing?
That would be annoying; often I try not to modify. I would go for:
maintain a modified variable for each file
add a * to the titlebar when modified
encourgae people to file bugs if the * isn't sensible
set modified flag when one of
adding a layer
changing a layer
modifying parameters:
(autoload, alpha, etc.)
waypoints, etc.
reordering layers
don't set modified flag on panning/zooming
when saving, do write the pan/zoom info
when ^S, do a save even if not modified (sort of covers the pan/zoom)
when ^Q or ^W, prompt for save if modified
possibly, add a global pref to say 'pan/zoom changes count as
modified' so those who want that can have them
pgpvFLgZyzaXs.pgp
Description: PGP signature
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
