[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [TSVN] how should the UI look like

From: Molle Bestefich <molle.bestefich_at_gmail.com>
Date: 2005-04-09 20:33:31 CEST

Rainer Müller wrote:
> Molle Bestefich wrote:
> > This is beyond "keeping dangerous features tucked away from the user".
> > It's a plain old treasure island "I want this gold treasure stuffed in
> > a place where only I can find it again! Mwa-ha-ha.." idea.
> >
> > Magic key combinations with no GUI equivalent were never a sane way of
> > doing things like this.

> You can even use it if you only have a keyboard.

Ok, so keyboard shortcuts are great for keyboard-only users. That's good.
But that doesn't make it sane GUI design!

> Maybe you don't know
> the way TortoiseCVS does it which is intuitive IMO.

The proposition made is to make the context menu appear different if
you hold a key while right-clicking whatever item in explorer. That
means that you'd have to hold SHIFT and press the MENU key next to the
WIN key, then scroll down to the TortoiseSVN sub-menu, and then you
would have a number of extra menu items to choose from.

Cmon, that's pretty far from intuitive.

> I just looked through the source of TortoiseCVS to find out how they did
> it. They just use the GetASyncKeyState API to determine if Ctrl is hold
> down.
> bool IsControlDown()
> {
> return GetAsyncKeyState(VK_CONTROL) < 0;
> }
> Couldn't we use that, too? So if you hold down Ctrl at the time clicking
> "Lock" it would force the locking (or display a dialog).
> We could even improve the UI more if we get rid of the "Update to
> revision..." entry and integrate that by holding down Ctrl and choosing
> "Update".

You're not stepping back one bit!
It's EVIL!

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Apr 9 20:42:06 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.