Cuperino
commented
1 year ago Loss of control bugs happen as a result of the cursor's focus on the prompter being lost when one interacts with menus. I've worked around this issue in the past by re-focusing the prompter through code after menu interactions. Another way of triggering this bug is to open and close a menu without interacting with it. The re-focus is hard coded for each interaction where applicable. It's done this way because Kirigami offers no means of tying code to the act of closing menus.
If you can see the Fullscreen button from windowed mode and you click on it, the prompter's focus gets restored as intended. The bug you've just discovered only happens when you have to open the menu to show the Fullscreen button in the first place.
The bad here news is "I didn't forget add the call to re-focus to full screen button", meaning the focus is lost after the button's code finishes executing, and the reason is probably related to the fact that the Fullscreen button is not in a sub-menu, but is a top-level button.
The good news are:
- All focus related issues will be gone for most systems once I re-write the inputs to use global-hotkeys, which is my main goal for v1.2.
- You can work around the issue today in two ways:
- Double click on the prompter to bring focus to the editor (the purple line at the button will turn green indicating you can now edit contents while prompting), then double click again to leave "edit while prompting mode" restoring focus to the prompter, allowing you to control it.
- Use a wider display resolution to ensure the Fullscreen button is visible at all times, meaning the restore focus will work as intended.
Bug Description No scroll control entering Full Screen mode.
Steps to Reproduce
Expected behavior Should behave the same with both methods.
Screenshots (optional) Raspbian Bullseye QPrompt 1.1.3