[TC 11.50b1] Key Up/Down navigating issues after deleting a folder in tree view

[cpp64]

These bugs have a relation with "[TC 11.03] When deleting a folder in the folder tree, the current line moves two steps."

TC 11.50-beta1 64bit
Windows 11 24H2 64bit

(A) --> (B) --> (C-1) // bug1
(A) --> (B) --> (C-2) // bug2
----------
[ directories ]
a
b
c // Pressing KeyUp once -----(C-1) // jumps up twice
-1
-2 // after deleting subdirectory 2 -----(A)
-3 // cursor moves to here -----(B)
-4 // Pressing KeyDown twice -----(C-2) // requires KeyDown twice to move to the next line
-5
----------

// bug1 : (C-1)
When pressing KeyUp once after deleting the current line directory, the current line jumps up twice.
------------------------------
1) Move to directory 2
2) Delete directory 2
3) Press KeyUp
--> Current line(directory 3) jumps to directory c, not directory 1

// bug2 : (C-2)
To move to the next line after deleting the current line directory, TC requires pressing KeyDown twice.
------------------------------
1) Move to directory 2
2) Delete directory 2
3) Press KeyDown
--> First KeyDown activates the current line on directory 3
4) Press KeyDown once more
--> Second KeyDown moves the current line from directory 3 to directory 4

[ghisler(Author)]

This should be fixed in 11.50 beta 2, please check!

[cpp64]

This should be fixed in 11.50 beta 2, please check!

"Separate Tree (Ctrl + Shift + F8)" is fixed.

"Tree (Ctrl + F8)" is not fixed.

[ghisler(Author)]

Not confirmed, cursor up/down works fine here also in tree in a file panel after deleting a directory.
Please explain what doesn't work.

[cpp64]

Not confirmed, cursor up/down works fine here also in tree in a file panel after deleting a directory.
Please explain what doesn't work.

I captured it.

// wetransfer (7 days), mp4
https://we.tl/t-ODNpHU7U5t

[white]

Confirmed for 64-bit only (not with 32-bit TC).

[ghisler(Author)]

Thanks, I can only reproduce it with a fresh ini file now.

[cpp64]

Confirmed fixed in TC1150b3.

[ghisler(Author)]

Thanks!

Moderator message from: ghisler(Author) » 2024-10-24, 08:22 UTC

Moved to fixed bugs