|
|
I can't reproduce this problem. Please tell me more detailed steps to reproduce. |
|
|
I will include a gif to demonstrate, but it is hard to see the blinking cursor. I promise it is blinking, though. -Open another program that has a text field in it, such as Discord or Notepad. -Open the menu of a ghost by double clicking them. (This puts the ghost in focus, and opening an input box at this point would work properly) -Click back into the other program you opened, and make sure you've clicked into the text field so that you can write. -Clicking on the *balloon only*, navigate through the ghost's menus and click an option that brings up an input box, such as changing the user's name. The cursor in the input box should be blinking, but since the ghost is not the window in focus, anything you type will go to the other open program instead. I think the best solution to this would be to make the focus switch to the ghost if a choice is clicked in the balloon, since that would ensure that if the user opened an input box by clicking on a menu choice they can type in it immediately. If that's not possible, it would also be acceptable for the cursor to not blink in this situation until the ghost is in focus. It really is a tiny problem, but it does cause embarassment now and then... When testing my input boxes, I usually just press a few random keys and send it before I have a chance to realize it's gone to the wrong program. And I am definitely not the only one who has done this. 21-8-13_02.gif (259,797 bytes) |
|
|
2.5.11 |
- Anonymous
