In the example video below I set cursor position via mouse in line # 78 next to sign "=", then I press Down key => result: cursor gets a position a little bit to the right instead of been strongly down (so, the physical X coordinate is not preserved).
I understand this can be somehow related to TABs, however, even if it is a case there is still inconsistency:
Meanwhile, if I set cursor position in line # 79 a little bit to the left of sign "=", then I press Up key, and Down key => result: cursor get a position strongly under the previous one, so for some reason in such case X coordinate is preserved.
This is very inconvenient. Physical X coordinate should be always preserved, even whether code contains TAB or not, and so on.
P.S. Perhaps, One rule should be as an exception: when cursor is located at the end of the line, when you press Up or Down it should also move to the end of the next next, not strongly vertically.
l4d_multi_witches.zip
In the example video below I set cursor position via mouse in line # 78 next to sign "=", then I press Down key => result: cursor gets a position a little bit to the right instead of been strongly down (so, the physical X coordinate is not preserved).
I understand this can be somehow related to TABs, however, even if it is a case there is still inconsistency:
Meanwhile, if I set cursor position in line # 79 a little bit to the left of sign "=", then I press Up key, and Down key => result: cursor get a position strongly under the previous one, so for some reason in such case X coordinate is preserved.
This is very inconvenient. Physical X coordinate should be always preserved, even whether code contains TAB or not, and so on.
P.S. Perhaps, One rule should be as an exception: when cursor is located at the end of the line, when you press Up or Down it should also move to the end of the next next, not strongly vertically.
l4d_multi_witches.zip