On 05.12.2010 14:29, Xuefer wrote:
> > i have an idea about tsvn shell context menu
> > there is setting for "cascaded context menu", when i check some
> of them,
> > the menu item would show directly in context menu instead of in
> > this is a great feature, however the accelerator key is conflict with
> > explorer built-in or 3rd party menu items. like tsvn &Diff vs
> > &Delete
> > the idea is, for any "cascaded context menu", give me an option to
> > remove any accelerator key shortcut that conflict with existing
> menu items
> > i prefer remove it from built-in menu items
> > IMHO simply enum each menu item and replace item text would work :)
> We will never change existing menu entries or entries from other apps.
> Just think about rule number one: "what happens if two apps would do
> it's immoral if software fight others for marking in this way
> but accelerator key conflict is a real life problem for the end users,
> like me, cancling conflict accelerator keys and keep tsvn one, is for
> users' good, there can be an option for this. either cancel tsvn's or
> the others', or do nothing
Since we can't know what happens if we modify other menu entries (the
app may only work if those are unmodified because it does a string
compare), we must not do this. Not even with an option.
> the tsvn's registry hack can disable tsvn's key but i want to keep it
> do we the users have to google around in hope of finding yet another
> context menu extension to solve conflict at our choice?
Or just ask the developers of those other apps to also provide an option
to have them remove their own accelerator keys.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-12-06 18:49:02 CET