octave-maintainers
[Top][All Lists]
Advanced

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

Re: have we ever been hit by a Qt bug while developing the Octave GUI?


From: Daniel J Sebald
Subject: Re: have we ever been hit by a Qt bug while developing the Octave GUI?
Date: Thu, 10 Jan 2019 22:51:02 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1

On 01/10/2019 01:07 PM, Carnë Draug wrote:
I am wondering if in the development of the Octave GUI we have been
hit by a Qt bug.  I don't follow the GUI related bugs with much
attention so I don't know but I don't remember seeing an Octave bug
that was actually a Qt bug.

So, have we ever been hit by a Qt bug while developing the Octave GUI?

Thanks
David



Yes. Early in 2018 a group of us tried to tackle an issue with floating a subwindow which then froze on, was it, KDE?. As a work-around there was a message placed in an old Octave version describing how to use control keys to move the window rather than the mouse. This turned out to be a mix of three or four issues, one of them being this Qt bug:

https://savannah.gnu.org/bugs/?53276#comment106
https://bugreports.qt.io/browse/QTBUG-44813
https://savannah.gnu.org/bugs/?53807

Furthermore, KDE Oxygen does not follow the convention that Qt calls out:

https://bugs.kde.org/show_bug.cgi?id=393076

KDE Oxygen is doing something a little strange in the fact they use Qt to create an implementation of Qt. That's possible to do, provide a certain group of functions related to graphics are supplied.

In summary, that collection of Qt/KDE floated window issues was a major effort--still with some workarounds until the bugs out of our control are addressed.

Dan



reply via email to

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