Opened 9 years ago

Last modified 9 years ago

#10847 new Bug report

Some buttons not shown properly in settings from Filezilla

Reported by: Geiger David Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc:
Component version: Operating system type: Linux
Operating system version:

Description

Hi,

Some of the functions of filezilla are not working properly:

Edit -> Settings -> Transfers -> Maximum simultaneous text is messed up
See screen captures:
https://bugs.mageia.org/attachment.cgi?id=7854

From https://bugs.mageia.org/show_bug.cgi?id=18535

Change History (8)

comment:1 by Tim Kosse, 9 years ago

Status: newmoreinfo

You are probably using an outdated version of wxWidgets.

Which revision of the WX_3_0_BRANCH of wxWidgets are you using? Have you yet tried updating to the latest revision from the repository?

comment:2 by Geiger David, 9 years ago

Status: moreinfonew

We are using the latest stable release of wxWidgets who is the 3.0.2 + some upstream patches

https://github.com/wxWidgets/wxWidgets/releases/tag/v3.0.2

http://svnweb.mageia.org/packages/cauldron/wxgtk/current/SOURCES/

comment:3 by Geiger David, 9 years ago

So, testing with latest snapshot from WX_3_0_BRANCH (commit 20160527):

https://github.com/wxWidgets/wxWidgets/commits/WX_3_0_BRANCH

And also testing with latest (unstable) 3.1.0 release

Issue is always there, neither of both has fixed the problem :(

comment:4 by Tim Kosse, 9 years ago

On closer look the text is rendered correctly. It's the spin button to the left of it that isn't rendered correctly

FZ uses a wxSpinCrl, a composite control of an edit field and a corresponding vertically stacked spin button. See http://docs.wxwidgets.org/stable/classwx_spin_ctrl.html for an example how it should look like on wxGTK.

I have no idea why the buttons are oriented horizontally instead and furthermore are painted outside the control's area.

In any case it's not a bug in FileZilla itself as vertical spin buttons aren't rendered correctly in wxWidget's widgets sample either, making it either a bug in wxWidgets or one of its dependencies.

comment:5 by Geiger David, 9 years ago

or rather a bug/config in new GTK3 3.20+ because on mga5 with exactly the same wxgtk3 and GTK3 3.14 there is no problem.

comment:6 by Tim Kosse, 9 years ago

Speaking of GTK3, any particular reason you are using the GTK3 configuration of wxWidgets?

Generally, wxWidgets with GTK2 results in much better looking programs, GTK3 tends to make everything looks ugly.

I think it's much preferable to configure wx with --with-gtk=2

comment:7 by Geiger David, 9 years ago

Any particular reason but many distributions have switched wxgtk3 compiled with GTK3 so we too :)

So now we have to decide what we will doing return back wxgtk3 to GTK2 or not :)

comment:8 by Geiger David, 9 years ago

So I come with good news:

Here we go! we have switched back to wxgtk3.0 built with GTK2 and now all works again as it should.

Thanks to pointed me that out :)

Note: See TracTickets for help on using tickets.