[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Release of Enigma 1.30-alpha

From: Andreas Lochmann
Subject: Re: Release of Enigma 1.30-alpha
Date: Sat, 26 Dec 2020 01:40:50 +0100

Hi Sidney,

I wrote a first draft of a manual relative mouse mode, in branch "alternative-mouse-input-1.3". You find the new button in the options menu, submenu "Config" (together with the other mouse related options). When you set it to "slow" it should work for you.

With "slow" and "fast" I refer to possible performance impacts. However, It turns out that the new "slow" method actually moves the marble slower. This was not intended. Even worse: Sometimes events are ignored. I reposition the (invisible) mouse cursor to the middle of the window on a regular basis. This generates a mouse motion event (because of cause manually moving the cursor generates an event -- it's not that the program wouldn't know, duh?), which has to be flushed. "SDL_FlushEvent" does not work for me, so, right now, I flush everything, including key strokes that happen in between. And maybe even additional, real mouse motion events, which would be the origin for the slowed down marble.

So, as of now, it's a hot-needle workaround.

Could you check if the "slow"-mode at least works for you? Thank you in advance.

Am Fr., 25. Dez. 2020 um 23:00 Uhr schrieb Sidney Markowitz <sidney@sidney.com>:
Andreas Lochmann wrote on 26/12/20 1:56 am:
> Hmm ... please change line 932 in video.cc from
>      SDL_SetRelativeMouseMode(enabled ? SDL_TRUE : SDL_FALSE);
> to:
>      SDL_SetRelativeMouseMode(SDL_FALSE);

This worked, though with the problem you mentioned when the invisible mouse
cursor leaves Enigma's window.

> Could you also try the following as replacement for line 932?
>    Log << "Result of SetRelativeMouseMode: " <<
> SDL_SetRelativeMouseMode(SDL_TRUE) << "\n";
> I assume that "enigma --log" yields something like
>    "Result of SetRelativeMouseMode: -1";
> Indicating an error.

No, the result of that is 0, and the large numbers problem of course re-appears.

> Oh, and is there a "Last SDL error:" at the end of the log (fourth line from
> the bottom)
> (Probably just "missing sound", but maybe it's an important hint.)

There is no "Last SDL error" in the log, and nothing in the log looks to me as
if it represents an SDL error message. There could be lines that I incorrectly
think are other warnings, but none of them strike me as being an SDL error


reply via email to

[Prev in Thread] Current Thread [Next in Thread]