Re: With set_event_compression, most recent motion event is held in waiting

From: Kjell Ahlstedt <kjellahlstedt gmail com>
To: JLM <jlyonm protonmail com>
Cc: "gtkmm-list gnome org" <gtkmm-list gnome org>
Subject: Re: With set_event_compression, most recent motion event is held in waiting
Date: Thu, 26 May 2022 16:53:39 +0200

Den 2022-05-26 kl. 14:07, skrev JLM via gtkmm-list:

Thanks for looking at this. I guess from what you say, you do not see
the problem. I understand, as I think it would become pretty obvious to
anyone for example running GIMP. So even if this isn't a problem
specific to my program, it may at least be a problem specific to my
environment.

But I do see the problem that you described. With event compression turned off, the last motion event is kept hidden somewhere in GTK until a key or a mouse button is clicked. I made the changes in gdkevents.c in order to find out if the missing motion event is held in GTK itself or in one of its dependencies.

I have written a bug report on GTK+ for now

https://gitlab.gnome.org/GNOME/gtk/-/issues/4946

References:
- With set_event_compression, most recent motion event is held in waiting
  - From: Jason M'Sadoques
- Re: With set_event_compression, most recent motion event is held in waiting
  - From: Kjell Ahlstedt
- Re: With set_event_compression, most recent motion event is held in waiting
  - From: JLM
- Re: With set_event_compression, most recent motion event is held in waiting
  - From: Andrew Potter
- Re: With set_event_compression, most recent motion event is held in waiting
  - From: JLM
- Re: With set_event_compression, most recent motion event is held in waiting
  - From: JLM
- Re: With set_event_compression, most recent motion event is held in waiting
  - From: Kjell Ahlstedt
- Re: With set_event_compression, most recent motion event is held in waiting
  - From: JLM

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