kicad-developers team mailing list archive

[jp charras <jp.charras@xxxxxxxxxx>]

Le 03/02/2018 à 18:54, Clemens Koller a écrit :
> Hi!
> 
> Simple solution: There is an wxpython-gtk2 in AUR. Use this instead of wxpython, as wxpython-gtk2 is linked against gtk2... blahblubb easy.
> 
> I am still wondering what's wrong with wxpython linking against gtk3 and why only KiCad seems to put it's foot in it?!

Perhaps because there are not a lot of complex applications using it.

> Can somebody explain more details about this wxDC stuff?

wxWidgets built against GTK3 has a very different wxDC stuff.

It is based (I am guessing) on cairo, and drawing modes needed by Kicad to draw moving objects (XOR
mode for instance) do not exists anymore.
I am guessing the new wxDC is similar to (or the same as) the "advanced" wxGraphicsContext.

And this is not only Kicad that exhibit issues:Test samples in wxWidgets using these wxDC drawing
modes (OR, XOR, and many others) also do not work anymore.

There is a much more annoying issue, clearly related to integer overflow in the GTK3 wxDC stuff:
Pcbnew (that uses large coordinate values) does not display correctly a board.
Eeschema does not fall into this bug, because it does not use large coordinate values

There are some other issues in GUI:
On KDE, some sizers are not correctly evaluated, giving broken dialogs.

> 
> Regards,
> 
> Clemens


-- 
Jean-Pierre CHARRAS