[TC 11.00b2] [Shift + F6] The cursor moves by 2 korean characters.

[cpp64]

# korean file/dir name
가나다라마바사아자차카타파하

Changing the korean file/dir name (가~하) with 'SHIFT + F6'

Pressing the key LEFT/RIGHT repeatedly

Cursor( | ) moves by 2 korean characters

|가|나다|라마|바사|아자|차카|타파|하|

[yyang]

And on Simplified Chinese Windows 10, the cursor fails to move to the left on Chinese text (not by any characters). Moving to the right is fine. Shift+Left doesn't work either. Ctrl+Left is OK (moving by words). Tested on both 32- and 64-bit versions. This is a major issue.

[Sir_SiLvA]

And on Simplified Chinese Windows 10, the cursor fails to move to the left on Chinese text (not by any characters). Moving to the right is fine. Shift+Left doesn't work either. Ctrl+Left is OK (moving by words). Tested on both 32- and 64-bit versions. This is a major issue.

Are you sure?
BETA 2 behaviour: (Ctrl+Shift+Left/Right is the same as Shift+Left/Right)
1) Shift+F6 -> Shift+LEFT once so you can in/decrease the selection from the LEFT side with Shift+Left/Right
2) Shift+F6 -> Shift+RIGHT once so you can in/decrease the selection from the RIGHT side with Shift+Left/Right

[yyang]

Yes, I'm quite sure.

[AntonyD]

2Sir_SiLvA
The problem is in the position of the blinking cursor. When I create a selection with the mouse, it also moves where I move the selection with the mouse. And if I work only with the keys from keyboard, then the selection is created, and the cursor does not move. And this is a paradox. I see that place - where editing should begin, but in fact I have to look at the opposite side of the selection, because the starting work area is there! Those there is a feeling that in this edit field there are now TWO control cursors. One just blinks, and the second - invisible - is always on the other side of the direction of movement I need.

[petermad]

2AntonyD

and the cursor does not move

Please see: viewtopic.php?p=430924#p430924

[AntonyD]

2petermad
Yes, now I remembered this topic But no matter how you look at cause and effect, the problem remains in the sense that despite the seemingly introduced new functionality, in fact it cannot be used. It does not work according to the usual canons. And in the end, there is only the possibility of disabling it (CtrlArrow=0). Those functionality seems to be there - but in fact it is not there and cannot be used. So why was it introduced then? This "broken" functionality?

[yyang]

@petermad Thank you! I can confirm CtrlArrow=0 "fixes" the issue I saw.

[ghisler(Author)]

This should be fixed in beta 3 even with CtrlArrow=1!

[pulbitz]

I've tested it, and the bug seems to be fixed!

[ghisler(Author)]

Great, thanks! I'm still setting CtrlArrow=0 as the default in beta 4. Those who need the extra stop characters will have to set CtrlArrow=1 themselves.