Il 04/06/22 19:59, Uwe Rathmann ha scritto:
[ Giuseppe D'Angelo wrote: ]
Properly signalling damage areas has a lot
of interesting use cases, from compositors to efficiently enable
remoting solutions (frame streaming/VNC/etc.).
Well, Qt/Quick is usually for modern user interfaces with smooth sta
Hi all,
sorry for hijacking a thread in a slightly different direction, but as
I was working on a VNC solution for Qt/Quick for EGLFS recently.
My VNC server ( BSD-3-Clause license ) can be found here:
https://github.com/uwerat/vnc-eglfs
The main reason why I'm not happy with the official VNC p
> On 4 Jun 2022, at 00:41, Giuseppe D'Angelo via Development
> wrote:
>
> Il 04/06/22 00:39, Shawn Rutledge ha scritto:
>> This might resemble the case when a TouchCancel event is sent: it means the
>> receiver should be un-pressed, undo whatever was done on press, and don’t
>> react otherwise
> On 4 Jun 2022, at 07:25, Philippe wrote:
>
> I have also noticed several posts on Stack Overflow, Qt Centre, etc, about
> this issue without a "real solution".
>
> I confirm. This case is very similar to user reports I've had for about 10
> years, on OSX only, that occur randomly. I've wast
> On 4 Jun 2022, at 00:08, Giuseppe D'Angelo wrote:
>
> On 03/06/2022 23:05, Volker Hilsheimer wrote:
>> If we were to deliver a mouseReleaseEvent to the widget that initiated the
>> drag via QDrag::exec after the exec returns, then we handle the
>> mouseReleaseEvent twice.
>
> Why twice? It
