Moving the discussion here. Jose Carlos Garcia Sogo wrote:
> 1. wouldn't make sense to have all checked and let the user uncheck > what he doesn't want? Depending if you copy many or not. This was done this way in my first implementation and found this painful. Let's here about others before switching back. > 2. would make sense to compress the history stack internally before > showing it to the user, so only the module in the last state can be > selected? Currently is a bit misleading if the same module is shown > several times. Right. Will try to do that. > Oh, and also select all (or select none if it is change) shouldn't be > select all and accept, IMHO. No strong opinion, I've done that to avoid a click. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_123012 _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
