[TC 10.0] Deletion / rename operations above separate tree item

[mosunovpa]

Deletion / rename operations above separate tree item are performed always for the selected item, not the one under the cursor.

[petermad]

Hmm, as far as I can see the item under the cursor in the Separate Tree is always selected, and I cannot select more than the curent item in the Tree.

But maybe I misunderstand you - I am not sure what you mean by "above".

[ghisler(Author)]

I wonder about that too - even if I check the option "Tree: Press ENTER..." in Configuration - Options - Display, the current item in the tree is always selected too.

[mosunovpa]

I mean you can use right click context menu above unselected item of the separate tree. And you expect "deletion" menu option will be applied to the item under the cursor. But the deletion (rename) action applies for current selected item.

[ghisler(Author)]

Yes, the context menu is always for the selected files and folders.

[AntonyD]

Yes, the context menu is always for the selected files and folders.

But mosunovpa said that context menu was issued

above unselected item

!
Thus your phrase means that current logic of TC is broken - it is allowable to issue the menu for a forbidden type of elements!

[petermad]

If I right-click on an item in the Separate tree, then that item gets selected BEFORE the context menu is opened - so it is obvious the folder it applies to it the selected one.

I cannot "select" more than the folder under the cursor in the Separate Tree - can anybody show me a screenshot with the cursor on another folder than the selected in the Separate Tree

[AntonyD]

Hmmm. It looks like you're right, but then it becomes unclear again - and what kind of incorrect behavior mosunovpa reported?
What does it mean:

you can use right click context menu above unselected item of the separate tree.

[ghisler(Author)]

It's a bug when using "Left mouse button selection mode": Then the right clicked item wasn't being selected, resulting in this error. There is no problem when using the default "Right mouse button selection mode".

[petermad]

It's a bug when using "Left mouse button selection mode":

Ha, that's why I could not reproduce it - I can confirm the problem with that setting.

IMHO if you use "Left mouse button selection mode" you might as well use Explorer.

[mosunovpa]

It's a bug when using "Left mouse button selection mode":

Ha, that's why I could not reproduce it - I can confirm the problem with that setting.

IMHO if you use "Left mouse button selection mode" you might as well use Explorer.

I think, behavior like in exlorer is convenient and expected. All operation in context menu above non selected item should be applied to this item, not selected one. And current selection should not be changed.

[petermad]

2mosunovpa

I think, behavior like in exlorer is convenient and expected. All operation in context menu above non selected item should be applied to this item, not selected one. And current selection should not be changed.

I agree, WHEN the users has set the Mouse selection mode to: "Left mouse button (Windows standard)". It is a bug and should be fixed - the problem was that this setting is not standard in TC - and you did not inform in your report that you were using a non standard (for TC) setting.

[ghisler(Author)]

Don't worry, I have already fixed it for the next beta.

[mosunovpa]

Thank you!!

[petermad]

08.05.22 Fixed: Right click on item in separate tree while using "Mouse selection mode" - "Left mouse button": The focus needs to be set on that item, otherwise some context menu commands may be applied to the wrong item (32/64)

Confirmed fixed in TC 10.50b5 Now right click in separate tree always selects the clicked item - also when "Mouse selection mode" - "Left mouse button" is enabled.