On or about 2009 Apr 8, at 12:00 AM, Steve Borho indited: > When the visdiff GUI is launched, it holds the temporary files in > place until our GUI is closed. This removes the requirement for the > tool not to fork an extra process, it no longer matters. However, > today we only launch the GUI when more than one file is diffable. If > only a single file is to be compared, we launch the diff tool directly > (less clicking, and all). > > So what I'm asking is whether you, the users, think removing this last > requirement on the diff tools outweighs the annoyance of bringing up > the selection GUI even when there is only a single file to be diffed? > > Thoughts?
I think it is a huge improvement either way. :) Hard to say, on paper, which is better, having a consistent UI or having a special case for fewer clicking. I think I would, abstractly, prefer to have the consistency, but I think either way works. -Doug ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
