Re: Desktop context menu whitespace

On Fri, Jan 29, 2010 at 16:37, Ethan McKinney <ethanm_at_broadcom.com> wrote:
>> Estimated time for you to actually create the registry key and right click on the desktop to check whether it works: half a minute.
>
> I'm not a developer. I don't screw with Registry entries unless I know that they're going to work. Especially because this is the company's computer, not mine.

Had you read the whole thread, you'd see that it's confirmed to work.
I didn't see anyone report that it doesn't work.

> I thought that providing specifics on possible conflicts could be useful. For example, a list somewhere of "if you have X installed, you're going to see this error" would save you (and others) a lot of time answering/arguing about the same problem in the mailing lists. It's really not necessary to reply this way.

This project cannot possibly maintain a comprehensive list of what's
compatible and what's not. To my knowledge, there is only one specific
piece of software which is documented as "not compatible" (certain
versions of PowerDesk), and then a general class of software which
*may* conflict - software which screws around with your context menus
with ridiculously large icons.

But to attempt to keep up with every display driver vendor and version
to track which versions cause this and which don't is just madness.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2443184

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-01-29 22:52:29 CET