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

Re: TortoiseOverlays 1.1.0

From: Adrian Buehlmann <adrian_at_cadifra.com>
Date: Thu, 18 Mar 2010 21:29:25 +0100

On 18.03.2010 21:01, Stefan Küng wrote:
> On 18.03.2010 20:57, Adrian Buehlmann wrote:
>> On 18.03.2010 20:39, Stefan Küng wrote:
>>> If a user decides to not have the ignored/unversioned overlays show up,
>>> then yes, they won't show up for any Tortoise client.
>>> But the user can as easily enable them again if needed.
>> But why only for ignored& unversioned ?
>> So can we then have the additional registry values:
>> HKCU/Software/TortoiseOverlays, ShowLockedOverlay
>> HKCU/Software/TortoiseOverlays, ShowReadOnlyOverlay
>> and drop the respective handlers in TortoiseOverlays irrespective of the
>> total number of registered handlers, if these registry values exist and
>> are set to zero?
> I haven't gotten around to implement this yet, but the plan is to have
> an option for *all* overlay handlers to get disabled.


But why not implement dropping locked and readonly via HKCU in
*TortoiseOverlays* in advance now? It would be an easy thing to
copy/paste the code lines for dropping ignored/unversioned and adjust
them to drop locked/readonly as well.

We could then set these registry values from the shell extension
settings tool of TortoiseHg (after all, we currently don't have
checkmark buttons for unversioned and ignored either, to compensate for
your change in TortoiseOverlays 1.1.0).


To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-03-18 21:30:45 CET

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.