2009/12/20 Rui Tiago Cação Matos <[email protected]>: > 2009/12/20 Yuki KODAMA <[email protected]>: >> Hmm... you didn't describe why it's *very* bad ui. >> Or you just want to see Stop button always? >> If you so, I'm okay to change the sensitive of Stop button instead >> of changing visibility :) > > I don't know why Adrian said so. But, for instance, the GNOME HIG has > this to say: > > "It is usually better to make a control insensitive than to hide it > altogether. This way, the user can learn about functionality they may > be able to use later, even if it is not available right now." [1] > > Rui > > [1] > http://library.gnome.org/devel/hig-book/stable/controls-sensitivity.html.en
I think I agree it's not good for buttons to appear and hide on their own accord. It does seem common for toolbars to come and go when an app changes modes, but not for buttons within an application to hide or become visible. Visual Studio changes it's toolbar sets when it changes modes, for instance. So you could make a case for the apply/discard buttons only being visible when the changelog is in bundle preview mode. But the buttons would need to be visually separated from the rest of the sync toolbar. -- Steve Borho ------------------------------------------------------------------------------ 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 _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
