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

Kjell Ahlstedt via gtkmm-list <[email protected]> Thu, 26 May 2022 16:53:39 +0200
Newsgroups	gmane.comp.gnome.gtkmm
Message-ID	<[email protected]>
This is a multi-part message in MIME format.
--===============3652867131877243126==
Content-Type: multipart/alternative;
 boundary="------------agRucldIyPg9FiLGEC4rtlPV"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------agRucldIyPg9FiLGEC4rtlPV
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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



--------------agRucldIyPg9FiLGEC4rtlPV
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix"><font size="2">Den 2022-05-26 kl.
        14:07, skrev JLM via gtkmm-list:</font><br>
    </div>
    <blockquote type="cite"
      cite="mid:[email protected]">
      <pre class="moz-quote-pre" wrap="">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.</pre>
    </blockquote>
    <font size="2">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.</font>
    <blockquote type="cite"
      cite="mid:[email protected]">
      <pre class="moz-quote-pre" wrap="">I have written a bug report on GTK+ for now
</pre>
      <br>
    </blockquote>
    <p><font size="2"><a class="moz-txt-link-freetext" href="https://gitlab.gnome.org/GNOME/gtk/-/issues/4946">https://gitlab.gnome.org/GNOME/gtk/-/issues/4946</a><br>
      </font></p>
    <p><br>
      <font size="2"></font></p>
    <br>
  </body>
</html>

--------------agRucldIyPg9FiLGEC4rtlPV--

--===============3652867131877243126==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
gtkmm-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/gtkmm-list

--===============3652867131877243126==--