x2 folder tree doesn't reflect changes

[MamiyaOtaru]

in .36 I notice that when I open a folder in the content pane, the tree view doesn't expand the folder I had been in. In other words, you can start out with c: totally unexpanded, and in the contents pane, click through to c:\windows\system32\drivers or whatever, and the tree pane doesn't change. c: remains unexpanded.

This is different from explorer and 2xexplorer. In other words, I don't ever want to have to click view->Locate in tree, I'd prefer that to be automatic, as it is in the file manager most people use, and in the one I use most (2x)

If this is on purpose, please have a checkbox or whatever in the options screen, whenever that appears (unless I'm looking in the wrong place?)

love being able to select columns in the detail view overall it's looking great.

[nikos]

you must have deleted the registry tweaks you did earlier
see FTCOPT_AUTOSYNCVIEW in alpha.txt

[mrjl]

how do i set up the registry tweaks in the first place. i've read the alpha.txt but can't understand it.

[nikos]

A. quit x2
B. open alpha.txt to have the values
C. let's take for example how to customize the tree. There's a single value called binTreeOptions as stated in alpha.txt. By setting it to various numbers you turn features on or off

this is something we do in programming a lot to save space. Say you had 2 adjustable options for the tree, single click activation and hover expansion. You could turn each on or off individually. In the simplest scenario you'd need two separate registry keys/values one each. Say one value called bSingleClick and the other bHoverExpand. If a value was set to number 1 then it would be considered on otherwise it would be off

now if you think about it this is kind of a waste of space since each (32-bit) value can hold many-many numbers and you only use it for 0 & 1. So the alternative is to use a single registry value to hold information for both features. So bit #1 would be about the single click, bit #2 for hover expansion, and so on up to 32 features could be packed.

whereas in the past you'd use a value 0 or 1 for the entire registry key, now you use individual bits. If you notice all the FTCOPT_xxx constant numbers described in alpha.txt, they all are values that turn a specific bit on/off (1 or 0).

that's the theory

practically now and taking the tree for example, if you wanted a tree to be single click activating, not hover expanding and be synchronized with the active view, you'd look up the FTCOPT_ constant numbers by name and add them together, and set this number to the registry value binTreeOptions. This number for this example is 1 + 8 = 9. Note that since we don't want hover expansion we haven't added 2, the value for FTCOPT_HOVEREXPAND

i suppose non-programmers will have a headache with all that but deliverance is coming in the end where most of these settings will be available throught the GUI

[JRz]

Please remember that X2 is still an alpha version and therefore not intended for inexperienced users!

So if you don't understand these matters perhaps it is wise to wait for the retail end user version

Nikos has to waste a lot of time to explain the features and thats not good! X2 has a long way to go although I'm using the alpha versions to my satisfaction for many months. So please: if you're prepared to be an alpha man, don't bug Nikos with 'trivial' questions (though I think Nikos himself doesn't mind, regarding his elaborate answer).

Nikos, keep on going. I like X2 more with every (alpha) release

Jan

[mrjl]

thank you Nikos. that help me a lot.