Tree/Tab Expansion Memory and Focus

Post by **admin** » 13 Apr 2007 09:28

peterbonge wrote:
admin wrote:Scriptable Hotkeys! This particular case might be a little extreme, but it would work like this. Each SH (Scriptable Hotkeys) points to a user-defined function which consists of two parts, an action and a parameter (modifier, variable...). Here are 3 examples, the first would be your wish:
Code: Select all
Action -----------------------------  Parameter
scroll tree selection to row [...]    3
goto                                  C:\
open                                  (path to any app/file)
You can map any key(s) onto these user-defined functions
That all sounds great. But I don't see how this helps me. Will I be able to use a user-function when doubleclicking on an empty tree area? Otherwise this wouldn't help me (in this case).

Currently I'm only concerned with keys. It's another idea to add customizable mouse actions... but let me finish the keys first.

What yould help you: find some other fool that supports your wish.

Post by **j_c_hallgren** » 13 Apr 2007 15:36

This is what appears on pg 3 of this thread:

j_c_hallgren wrote:
peterbonge wrote:But I (we?) think it would be nice if this value would also affect the double-click-scrolling.
As I stated right before your "hello mr admin" post, I'm convinced having dbl-click work differently from tab-switch is a good thing, even though I use it very rarely...now maybe the (ugly) solution to this would be another INI setting?

Which does seem to say that I agree with peter's requested solution, even though I'd (and many/most others, maybe?) likely never use it...as peter has different needs and uses product differently than I do....so does that make me a fool?

surrender · Post by **surrender** » 13 Apr 2007 15:52

I somewhat agree with peter and jc. Some prefer first row and some prefer customisable row, quite valid if you ask me.
I might be a fool but the wish doesnt seem foolish.

Post by **j_c_hallgren** » 13 Apr 2007 16:18

BTW, I'd also suggest instead of "No UI", in INI comments, the marker be "Tweak", as "No UI" was another of those "huh?" literals...same nbr of chars, and very easy to spot/find.

Post by **admin** » 13 Apr 2007 18:55

Okay, I did it just to kep you all quiet!

No comment in the history nor in the help file. And only on DblClick, not on Shift+F6.

And: you have to find the "Tweak" in the INI by yourself

peterbonge · Post by **peterbonge** » 15 Apr 2007 23:05

I found it! I found it!

Thanks!

Maybe it would make sense if TreeRowForDblClickScroll would also affect the doubleclick scrolling in the list view. It's just a thought.

jacky · Post by **jacky** » 16 Apr 2007 21:51

peterbonge wrote:Maybe it would make sense if TreeRowForDblClickScroll would also affect the doubleclick scrolling in the list view. It's just a thought.

Yeah.. I was actually thinking the same, since this setting exists, it would make sense to either rename it to "RowForDblClickScroll" and use it for List as well, or have a "ListRowForDblClickScroll" too.

Also, I think it should work as TreeRowForAutoScroll does, meaning when set to 0 it should scroll as little possible. For consistency sake, and because having TreeRowForDblClickScroll=0 for first row can be confusing a bit, no?

And while I'm a PITA:
- There's now "; Tweak: " for [General]UnitByte, but no interface either.
- Same goes for [NewTemplates] (FolderN, FileN)
- I know it was only because there's no pressed state, and it's not really "obvious"/visible otherwise, but since you update the tooltip for Show/Hide Hidden Items, why not do it on all show/hide's (panel, catalog, etc) (or, make a pressed state

)

[/PITA]

Post by **admin** » 16 Apr 2007 22:01

jacky wrote:
peterbonge wrote:Maybe it would make sense if TreeRowForDblClickScroll would also affect the doubleclick scrolling in the list view. It's just a thought.
Yeah.. I was actually thinking the same, since this setting exists, it would make sense to either rename it to "RowForDblClickScroll" and use it for List as well, or have a "ListRowForDblClickScroll" too.

Also, I think it should work as TreeRowForAutoScroll does, meaning when set to 0 it should scroll as little possible. For consistency sake, and because having TreeRowForDblClickScroll=0 for first row can be confusing a bit, no?

And while I'm a PITA:
- There's now "; Tweak: " for [General]UnitByte, but no interface either.
- Same goes for [NewTemplates] (FolderN, FileN)
- I know it was only because there's no pressed state, and it's not really "obvious"/visible otherwise, but since you update the tooltip for Show/Hide Hidden Items, why not do it on all show/hide's (panel, catalog, etc) (or, make a pressed state )

[/PITA]

Hey, do you want CKS or not?

And what is "TreeRowForDblClickScroll", never heard of this option

Post by **j_c_hallgren** » 18 Apr 2007 20:37

BTW, The other advantage that I just realized about using literal 'Tweak' as I saw you did in INI (Thanks!

) is that it makes finding threads here related to it easier as the search function can now find it...

Post by **admin** » 18 Apr 2007 20:39

j_c_hallgren wrote:BTW, The other advantage that I just realized about using literal 'Tweak' as I saw you did in INI (Thanks! ) is that it makes finding threads here related to it easier as the search function can now find it...

Yep, I like it! Thanks for the idea.

Buttonpusher · Post by **Buttonpusher** » 25 Apr 2007 02:30

When I started this thread I thought it was going to die! Since I have been on the sidelines I just wanted to say thanks Don, for the "Tweaks":)