Tree and List - Autospacing and INI key request

[Mesh]

Since XY autosets the spacing of the Tree and List panes based on whether it's being run on a pre or post Vista version of Windows, things are now more complicated than before.

If XY is run on Win 7, for example, it autospaces itself to a wider spacing. If the user then manually drops the spacing down to what it used to look like (and what it looks like if it's run on XP), it's safe to say that that's how the user likes XY to appear.

So far, that's inconvenient, but acceptable.


The problem is that XY doesn't set the INI keys for the Tree/List spacing as an absolute value, but as a relative one (e.g. "-2"). So now, if that version of XY is a portable version, and is subsequently run on XP - it autospaces itself to the normal XP spacing, *then* adds on the relative value in the keys - which means, for this example, that XY would be running with the spacing of "XP - 2" or "Win 7 - 4".


I would request that once the Tree/List spacing is adjusted manually, that XY freezes it at those settings, and does not try to autospace itself anymore, regardless of what O/S it finds itself running on. Alternately, run the autospace routine only once - on the very first run of an XY installation.

I would also request that the spacing to be an absolute value, rather than a relative one - for the sake of clarity. After all, "-2" on XP is clearly not the same as "-2" on Win 7.

[admin]

It is stored relative because also the fontsize plays a role here.

Win7 is wider than XP, and XY reflects this like many other software.

The only way I see is a tweak to suppress the Win7-auto-spacing in XY.

[Mesh]

The only way I see is a tweak to suppress the Win7-auto-spacing in XY.

I'll take it!

[admin]

Sorry, but I have to say no. Not really worth it. Gotta draw a line. Will wait for second fool.

[Mesh]

Sorry, but I have to say no. Not really worth it. Gotta draw a line. Will wait for second fool.

I'm not sure I understand the "fool" comment, but do you mind if I ask why you think this isn't worth doing?

I often move between Win 7 and XP, but I like the way XY looks on XP.

If I configure it properly for Win 7, then as soon as I run XY on XP, everything is squished. And if I fix it while I'm in XP, then as soon as I run it in Win 7, everything is expanded.

XY was specifically designed to be portable - shouldn't it maintain a stable UI between O/S's?

[j_c_hallgren]

Sorry, but I have to say no. Not really worth it. Gotta draw a line. Will wait for second fool.

I'm not sure I understand the "fool" comment,

It's Don's way of saying that it needs a second user here to request the same thing...don't be offended by it...some have, but it's meant kindly.

[admin]

Sorry, but I have to say no. Not really worth it. Gotta draw a line. Will wait for second fool.

I'm not sure I understand the "fool" comment, but do you mind if I ask why you think this isn't worth doing?

I often move between Win 7 and XP, but I like the way XY looks on XP.

If I configure it properly for Win 7, then as soon as I run XY on XP, everything is squished. And if I fix it while I'm in XP, then as soon as I run it in Win 7, everything is expanded.

XY was specifically designed to be portable - shouldn't it maintain a stable UI between O/S's?

Win7 is more expanded than XP. I cannot help it. You opt to go more narrow than the OS defaults. No problem, XY allows you to do that. And this wish of yours is even portable: you will also go more narrow in the other OS. Looks alright to me.

Conc. fool: search for "two fools rule" here in the forum.

[Mesh]

Win7 is more expanded than XP. I cannot help it.

I find it funny that you say that, since before you added the autospace routine, XY *wasn't* more expanded than XP when run on Win 7.

You opt to go more narrow than the OS defaults. No problem, XY allows you to do that. And this wish of yours is even portable: you will also go more narrow in the other OS. Looks alright to me.

Forgive me, but you're not looking at this correctly. My (and any other user's) desire for how XY looks is *absolute*, NOT relative. If I like 5 pixels of space seperating each line (just picking a random number out of the hat), then I like 5 pixels of space regardless of the O/S. It is not correct to make this a relative judgement saying that I want XY narrower than the O/S - regardless of whatever the O/S default is. That is not correct, and it is not portable.

Let's turn this around - do you want XY's icon colors to be based on the *difference* between RGB hue values from the Start Menu button colors of whatever O/S XY is run from? Or do you want it to be the same *absolute* RGB values regardless of what O/S XY is run from?

It's no different here.

[admin]

Yep, convinced. I'll find a way...

[Mesh]

Yep, convinced. I'll find a way...

As always, much appreciated.

Thanks!