|
From: Fernando G. L. <fer...@gm...> - 2020-12-27 03:41:35
|
Indeed, I didn't notice until now that another window was being
created that "sucked" all input. I'm also getting some console output
related to Sview, which aligns with my suspicion that this bug was
introduced after the Compositor was made default.
1.32 [ALRT]:general SviewGetEventViewport() returned nullptr
is being spammed in the console on multiple camera setups (doesn't
have to be multiple windows, having multiple cameras is enough to
trigger the input bug/console spam).
Maybe Jules can provide some input? No pun intended :)
Fernando
On Sat, Dec 26, 2020 at 1:37 PM Durk Talsma <dur...@gm...> wrote:
>
> Hi everybody,
>
> today, I believe that I might have found the culprit, with respect to flightgear losing mouse / keyboard focus in multiscreen configuration.
>
> I reconfigured my desktop so that I could run in the multiple screen / multiple camera configuration and started flightgear (from the launcher) using an old monitor configuration file. In my systems' configuration, the left monitor is XScreen 0, the center screen is XScreen 1, and the right one is XScreen 2. When launching flightgear, initially everything works fine, until the "loading scenery" stage, when another black window appears. This new window, which was not in fullscreen mode, effectively appears to capture all the mouse and keyboard input.
>
> In order to not make this description too long, I tried uploading a short movie of my systems' behavior, which you can find here: https://we.tl/t-D33E5QWqZf
>
> Please note, that this was an initial test; the left window is on a completely wrong monitor... :-)
>
> Any ideas whay might cause this?
>
> Cheers,
> Durk
|