kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #02690
Re: wxAUI patch (aui.patch)
-
To:
Marco Serantoni <marco.serantoni@...>
-
From:
jean-pierre charras - INPG <jean-pierre.charras@...>
-
Date:
Tue, 09 Jun 2009 16:21:04 +0200
-
Cc:
kicad-devel@xxxxxxxxxxxxxxx
-
In-reply-to:
<b84e40100906090230i11c058e1u1debf81968ae4564@...>
-
User-agent:
Thunderbird 2.0.0.21 (Windows/20090302)
For developpers info, copy to kicad devel group.
Marco Serantoni a écrit :
On Tue, Jun 9, 2009 at 9:50 AM, jean-pierre charras -
INPG<jean-pierre.charras@...> wrote:
Marco Serantoni a écrit :
Jean pierre, the patch in subject is in reviewing or was rejected ?
If there are problems of any kind political, social, about code style or
malfunctioning in any platform let me know also in the most rude way.
I wish cleanup my working svn to proceed to other things and i'm blocked
No problem indeed!
Just i had a lot of work last days, and did not tested the patch very well.
Problems i found could be due to a lack of refinement in the patch (it was
just an attempt, i believe, to use wxAUI).
They are:
- Last tool not visible (only its left side is visible) on all toolbars.
I've add a to toolbars an extra separator for this reason, problem is
not existant on wx2.9.
I tested it with wx2.8.10.
I'll test the wx2.9 version ASAP.
- Under Windows only, the left vertical toolbar (option toolbar)seems not
floating on parent,
so when it is moved to to panel area it diseappears after the first window
refresh.
wxAUI could be very useful for the new Layers dialog we are thinking about
Seems also crashes when exiting (destructors problems ?), and cvpcb crashes
when opening the 3D wiever.
I were unable to test cvpcb due known problems with wxFLOAT_ON_PARENT
with OSX and i'm testing how it works with wx2.9 but sadly works a bit
better but still having problems.
For the destructor problems if you want i can try to move the UnInit()
in drawframe.cpp directly.
In fact I did not investigate this problem, and I do not know exactly
what happens.
This problem looks like a destructor problem, but not sure this is
really the case.
I planed to run kicad in debug mode with GDB to see what exactly happens.
So no problem to use new wxAUI items, but ( as you said in a previous mail,
and like in your patch) use conditionnal compilation to use (or not) wxAUI
toolbars, at least until these issues are solved
--
Jean-Pierre CHARRAS
Maître de conférences
Directeur d'études 2ieme année.
Génie Electrique et Informatique Industrielle 2
Institut Universitaire de Technologie 1 de Grenoble
BP 67, 38402 St Martin d'Heres Cedex
Recherche :
Grenoble Image Parole Signal Automatique (GIPSA - INPG)
Grenoble France