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

Bug#894663: transition: wxwidgets3.0



On Mon, 16 Sep 2019, Gunter Königsmann wrote:

 *  Scroll Wheels and Two-Finger scroll are broken in this
combination, if
    Wayland is used (934386) and

Is two finger scrolling really a high priority issue?  It seems like a
nice to have rather than a must-have IMHO.

 *  If a horizontal scrollbar is visible all custom controls (e.G.
    wxMaxima's worksheet) flicker badly (934386)

On this issue, I'm not convinced that upstream can reproduce it, based
on the comments in the ticket.  I don't think that I've reproduced it
either. Since you claim that it doesn't occur with wx 3.1, can you do
a bisection between wx 3.0 and 3.1 to determine which commit fixed
it?  If we can figure that out, we can backport the patches.

Vadim (who is one of the maintainers) can reproduce it. I cannot
guarantee, though, if the right graphics card/GTK version/something else
needs to be used in order to trigger the bug. Or if this is one of the
esoteric bugs that only affect a handful of users.

You are right, he did say that. He also said he didn't know if he would have time in the near future to look into it. So, what you say about trying to bisect the issue?

If wxMaxima otherwise would be dropped from debian I am willing to
switch
to a flickering version that uses GTK3. But if I don't occur this risk I
would rather stay at GTK3 until wxGTK 3.2 is released - which will
fix this
issue. The wxWidgets maintainers told me that wxGTK 3.2 will be released
"soon". But the same was true a year ago - which I normally would be
fine
with: wxGTK 3.1 works fine, the combination of wxGTK 3.0 and GTK2 works
fine, too - and it is wise to release a library when it is ready, not
according to an arbitrary schedule.

Well, there is still time to fix the issues - Bullseye release is
still a long way off.

And yes, upstream wx claims that wx 3.2 will be "soon" but we have
heard that for a long time.  :)  So I don't think we can depend on that.

That only partially answers my question. Currently I am playing with the
thought if the right idea would be uploading a wxMaxima version that
uses GTK3 to debian testing and looking if anyone except Vadim and me is
affected by the bug.

Well, the only thing we can control is that the GTK2 build of wx will be gone in Bullseye, barring any unforseen circumstances. Whether that will be with wx 3.0 or wx 3.2, remains to be seen.

Scott

Reply to: