On 10/27/2017 10:02 PM, hauptmech wrote:
> On 28/10/17 01:00, Wayne Stambaugh wrote:
>>> If the pane is mandatory (no view toggle) you probably need to hard-code
>>> unhiding it after LoadPerspective to be nice to users upgrading with
>>> config files in place.
>> You will most likely have to
Le 28/10/2017 à 04:02, hauptmech a écrit :
> On 28/10/17 01:00, Wayne Stambaugh wrote:
>>> If the pane is mandatory (no view toggle) you probably need to hard-code
>>> unhiding it after LoadPerspective to be nice to users upgrading with
>>> config files in place.
>> You will most likely have to
On 28/10/17 01:00, Wayne Stambaugh wrote:
If the pane is mandatory (no view toggle) you probably need to hard-code
unhiding it after LoadPerspective to be nice to users upgrading with
config files in place.
You will most likely have to force the change in the perspective to
ensure that you can
On 10/27/2017 2:04 AM, hauptmech wrote:
>
> That must have been painful to find...
>
> A quick read of the Aui code says yes there is a problem. They hide all
> panels at the beginning of LoadPerspective and then update only panels
> with keys in the configuration string. So anything new and not
That must have been painful to find...
A quick read of the Aui code says yes there is a problem. They hide all
panels at the beginning of LoadPerspective and then update only panels
with keys in the configuration string. So anything new and not in the
config file will stay hidden.
I'm not
I finally discovered the issue. To add a new wxAUI pane, I had to go into
~/.config/kicad/pcbnew and delete all entries relating to modview. After
this, I was able to see the new item.
So, is there is a potential problem with wxAuiManager::LoadPerspective, if
the layout configuration has changed?
Looks like I missed modview_frame at the time so you'll want to
reference one of the other frames and update it. I converted a lot of
erroneous Row() calls to Layer() and standardized the initialization. On
the git repo it's commit bd19d31082...
Remembering more about this now. From back when
It looks like I left some notes in wxstruct.h/class EDA_PANEINFO way
back when I set up moveable toolbars for my branch... Not sure if they
are relevant as this has long faded from my memory.
On 16/10/17 15:00, Oliver Walters wrote:
The image is 1920x1020, there should be no issue reading the
And, I have only been able to create the window undocked and I can manually
dock it. I also have not figured out how to programmatically undock it either..
I figured out the code sequence largely by trial and error.
Greg S.
> On Oct 15, 2017, at 9:19 PM, Greg Smith
The following code in python creates a docked window:
https://github.com/HiGregSmith/LayerViewSet/blob/master/layerviewset.py
See the class "gui" and the function "Run".
You have to find the AUIManager and add an AuiPaneInfo as well as set the
parent. It's a little tricky.
I hope this helps.
The image is 1920x1020, there should be no issue reading the text...
Anyway, the issue is that I have tried to add a new panel to the module
selector window, by copying the code used to add the panels that are
currently there. Compiles ok but when I run KiCad and open the selector,
the new panel
I can't read the text, there's not enough resolution. What is the issue?
I've had windows that seem to be tucked under the horizontal toolbar.
Greg S.
> On Oct 15, 2017, at 7:46 PM, Oliver Walters
> wrote:
>
> I'm trying to add a new panel to the module viewer
I'm trying to add a new panel to the module viewer window. "screenshot"
below.
However I can't get wxAUI to play along at all. I cannot even get a new
panel to be displayed in this window. Are there any particular tricks that
may be non-obvious?
https://i.imgur.com/dXj51u1.png
Cheers,
Oliver
13 matches
Mail list logo