Project

General

Profile

Bug #3437

Updated by unseeingwhale about 10 years ago

(This bug is partly a duplicate of Bug #1230 but updated for 0.25)

This bug's issues lead to issues of "click through UI" and "not captured data entry".

To reproduce keyboard bug (1):
- Go to VAB
- Select any root part
- (1) Go to vehicle name field or description field and enter the letter "x". Watch how symmetry mode changes with each keypress, while the letter is also entered in the field.
- (2) Go to vehicle vihicle description field and try to use "return" key for line break. It does not work.

Another keyboard bug (2):
- Launch a flight with only the Mk1-2 Command Pod
- Right click on the pod and select "Rename Vessel"
- Enter the letter "c" in the name field. The view switches to IVA view.

To reproduce mouse bug (3):
- Go to VAB
- Select a large root part (i.e. Mk1-2 Command Pod)
- Scroll down view until Command Pod is beneath vehicle name field.
- You can now right click through the name field or the description text field.

Another mouse bug (4):
- Launch a flight with only the Mk1-2 Command Pod
- Right click on the pod and select "Rename Vessel"
- Move the mouse over the pod and watch it being highlighted in green even if the mouse is over the renaming UI window. (Compare this behavior with the right click dialog itself. Here the mouse is captured by the UI properly)

Both bugs seem to be related with the UI not capturing inputs iputs properly. The behavior is very much pronounced when using addons/mods which require data or text entry and heavily affects afffects KSP's usability. They are however very visible in the game itself.

This bug is related to both, mouse and keyboard behavior and might be split into two bugs.
This bug should be considered high, as it is a bug at a very low level regarding most of the UI.

How KSP should behave:
- Example 1 (Keyboard): While a cursor is active (any text entry), the keyboard entries should be fully captured.
- Example 2 (Mouse): In the building selection menu right click on a building (i.e. VAB). A context window pops up. It properly captures the mouse and does not allow click through. (It captures the mouse whereever on the screen it is)
- Example 3 (Mouse): In the same view open the contracts overview. Rotate the view so that some clickable building is beneath the contract list. Now you cannot click through. (It does not capture the mouse completely, you can still highlight/click on the buildings outside the contract list)
- Example 4 (Mouse): Start a flight with the Mk1-2 Command Pod only. Right click the pod. Move the mouse in and out of the context menu. The pod will only be highlighted when the mouse is outside the menu. This should be true to all UI elements!

Back