So, pretty much every time I use the the Ctrl+Shift+F to 'Search Again', this happens. The Up-Down Command History buttons on the Input Bar move to the right side and text starts to enter on the right side... but not /just/ that.
If I start to scroll through command history using the buttoms, randomly it crashes. If I switch World windows using Ctrl+Tab, only the one World input bar is affected, and eventually upon switching back to the affected one, it switches back to normal. Upon experimentation, almost every command that uses Ctrl+Shift+(anything) causes this bug to occur.
When entering text, it starts on the right /side/ of the bar, but the text still enters from the left to right, then after hitting space to move to the next word, the cursor goes all the way to the left of the text, still on the right side of the bar, with one space obviously cause you just hit space. However, when you type again, it moves the cursor back to the very very right and enters text left to right again. The only exception, is when you enter symbols like # instead of text or numbers. Then it inputs it on the very left, as it did with the spaces. But then, corrects itself when you type a normal letter or number again.
Here is a screenshot:
http://www.elraver.com/bug20070313.jpg
Those words were typed in the order of First, Second, Third, and #####, without a space after the #####. The screenshot couldn't seem to capture the cursor, but it is currently resting and blinking on the left side of the #####.
elraver
If I start to scroll through command history using the buttoms, randomly it crashes. If I switch World windows using Ctrl+Tab, only the one World input bar is affected, and eventually upon switching back to the affected one, it switches back to normal. Upon experimentation, almost every command that uses Ctrl+Shift+(anything) causes this bug to occur.
When entering text, it starts on the right /side/ of the bar, but the text still enters from the left to right, then after hitting space to move to the next word, the cursor goes all the way to the left of the text, still on the right side of the bar, with one space obviously cause you just hit space. However, when you type again, it moves the cursor back to the very very right and enters text left to right again. The only exception, is when you enter symbols like # instead of text or numbers. Then it inputs it on the very left, as it did with the spaces. But then, corrects itself when you type a normal letter or number again.
Here is a screenshot:
http://www.elraver.com/bug20070313.jpg
Those words were typed in the order of First, Second, Third, and #####, without a space after the #####. The screenshot couldn't seem to capture the cursor, but it is currently resting and blinking on the left side of the #####.
elraver