That is an interesting question. Was not aware of the GTK3 vs. GTK2. I
thought it seemed to run Ok but I admit had not used it in anger.
it does have a few little ‘visual’ issues. Like in pcbnew the layer
colour buttons seems to have too much inside margins and the colour is
now just a small vertical sliver. And in eeschema I have a ghost trail
of the cursor.
I ‘assumed’ that some of these were to do with that I was running Fedora
as a VM rather than native but it quite well be this GTK3 vs. GTK2 thing
:-(.
I had setup the Fedora VM a platform to more easily debug in KiCad as I
am still struggling to get ‘debug’ to work under Windows.
If you don’t use the legacy canvas on a system using wx with gtk3, you are not too affected on the crappy wx3 and gtk3 integration. Exact cause and fix unknown.
Legacy Canvas and Wxgtk
The legacy canvas has problems with wxwidgets 3.0 built with gtk3, this combination is usually called wxgtk on various package distributions. Don’t be confused when you see wxgtk 3.0.0 in your package manager, this is usually reffering to the wxwidgets version, and not weather or not it is built against gtk3.
It has been seen that fedora 20, 21 and 22, builds against gtk3 and you will experience the symptoms described below.
The symptoms, is that eeschema zooming will be slow, and the graphics is not quite exact, try looking at the grid dots. And in pcbnew, the canvas does not really draw near properly at all.
nickoe, thanks for that info. On one of my systems ( xfce fedora 22 in VitualBox ) the build as described by MarcoHess worked perfectly, and no issues as you describe.
Now on my main system, a fresh xfce fedora 22 bare install, using the same recipe above, I see the symptoms as you describe. Zooming very slow, + + + symbols all over the path the cursor takes. Very unusable. I will read your full post to see if there is a solution., Until then, i installed the version in copr and it seems ok.
UPDATE:
Followed information from nickoe links did this: 01-fixkicad.conf
re-built and it works perfectly.
( I am running an old AMD dual core w/ radeon video. )
(( my host for the vbox that worked is a windows host , on intel. so it did not have this issue)