Re: [Kicad-developers] wxAUI woes

[Wayne Stambaugh]

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 force the change in the perspective to
>> ensure that you can unhide panes.  I would be careful about what aui
>> behavior you enable.  If I recall, detachable panes was also broken but
>> that make have been fixed.  Have you tried testing with wx 3.1?  Maybe
>> the wx project fixed some of these issues.
>>
> Internal to Aui, there is no such thing as a perspective. It's just just
> the name used to load and save all the pane (and dock) info.
> 
> It's been a long time but my recollection is that Aui worked fine once I
> read the [aui] code and got an understanding of how it was designed to
> be used. The written documentation was sparse and kicad authors had
> misinterpreted some of how Aui is supposed to work. EDA_PANEINFO
> (kicad/include/wxstruct.h) captured much of what I learned. My goal at
> the time was detachable panes, which worked without problem once the
> panes were configured properly. My patch left out the final setting for
> detachable panes because everyone was gunshy about aui at the time and
> it was too big a step.
> 

I got detachable panes and toolbars to work as long I didn't use the
perspectives to save/load the state of the UI between sessions.  This is
where things fell apart.  To be honest, I didn't spend a lot of time on
this and I certainly didn't dig through the wx source.  I was just going
by the wx documentation.

As long as you manage to save/load the UI settings between sessions, I
am fine with making these changes.  Allowing the UI to be changed
without saving the changes between sessions doesn't make a lot of sense
to me so I would rather not go down that path.  If you do take on this,
please limit the changes to one main frame and get it working properly
before applying it to all of the main frames.

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] wxAUI woes

[jp charras]

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 force the change in the perspective to
>> ensure that you can unhide panes.  I would be careful about what aui
>> behavior you enable.  If I recall, detachable panes was also broken but
>> that make have been fixed.  Have you tried testing with wx 3.1?  Maybe
>> the wx project fixed some of these issues.
>>
> Internal to Aui, there is no such thing as a perspective. It's just just the 
> name used to load and
> save all the pane (and dock) info.
> 
> It's been a long time but my recollection is that Aui worked fine once I read 
> the [aui] code and got
> an understanding of how it was designed to be used. The written documentation 
> was sparse and kicad
> authors had misinterpreted some of how Aui is supposed to work. EDA_PANEINFO
> (kicad/include/wxstruct.h) captured much of what I learned. My goal at the 
> time was detachable
> panes, which worked without problem once the panes were configured properly. 
> My patch left out the
> final setting for detachable panes because everyone was gunshy about aui at 
> the time and it was too
> big a step.
> 

I also don't think Aui is broken, but (as you said) it suffers from a lot of 
missing doc, so when
something goes wrong, it is hard to know what really happens.

From my experience:

- Load/Save perspective works fine *only* when there is no change in widgets 
(toolbars and their
items) because it saves/restore all setup, and this setup can create conflicts 
if a config has
changed after the last save.
Especially, we have issues in main toolbar of the footprint viewer because one 
tool (export tool)
was displayed or not.
In this case, the kicad code must handle some parameters (size for instance)
- Detachable panes seriously modify the way events are managed inside the pane, 
especially in modal
dialogs or wxFrames:
For instance the main toolbar of the footprint viewer can be detached.
When it is detached, it is inside something like a miniframe.
Now consider what happens in modal frames: the wxWidgets (and the initial Kicad 
code in ShowModal()
) disables all windows but the modal frame itself (and changes the event loop).

Therefore the "miniframe" is disabled and cannot be used.
However this is not a Aui issue.

I fixed that in kicad code by reenabling all top level windows that are child 
of the Kicad frame
shown in modal mode ( in fact the miniframe containing the detached pane ).
This is a kind of issue easy to fix but tricky to understand, and in this case 
the first idea is
often: AUI is broken.

Using detachable panes can have an interest in complex cases because when used 
in a miniframe, I am
thinking this miniframe (a top level frame) receive all EVT_CHAR_HOOK, and I am 
not sure this is the
case when the pane is not detached (is docked) because accelerator keys capture 
some key events.

But how EVT_CHAR_HOOK is exactly managed depend on the platform.

-- 
Jean-Pierre CHARRAS

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] wxAUI woes

[hauptmech]

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 unhide panes.  I would be careful about what aui
behavior you enable.  If I recall, detachable panes was also broken but
that make have been fixed.  Have you tried testing with wx 3.1?  Maybe
the wx project fixed some of these issues.

Internal to Aui, there is no such thing as a perspective. It's just just 
the name used to load and save all the pane (and dock) info.


It's been a long time but my recollection is that Aui worked fine once I 
read the [aui] code and got an understanding of how it was designed to 
be used. The written documentation was sparse and kicad authors had 
misinterpreted some of how Aui is supposed to work. EDA_PANEINFO 
(kicad/include/wxstruct.h) captured much of what I learned. My goal at 
the time was detachable panes, which worked without problem once the 
panes were configured properly. My patch left out the final setting for 
detachable panes because everyone was gunshy about aui at the time and 
it was too big a step.





___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] wxAUI woes

[Wayne Stambaugh]

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 in the
> config file will stay hidden.
> 
> I'm not current on kicad gui policy.  That said, everything works as I
> would expect it to.
> 
> A user with an existing config will keep that config and can use the
> pane toggle in the view menu to turn the pane on.
> A new user will have an empty config file and will get the default
> config as defined in the code.
> 
> Going forward  LoadSettings() or SaveSettings() probably need a property
> filter added, as those are where SavePerspective (and LoadPerspective
> once Dick finishes per his comment in the code) are called.

I think I'm the one who used {Load/Save}Perspective.  Dick commented it
out when we discovered it was broken.

> 
> 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 unhide panes.  I would be careful about what aui
behavior you enable.  If I recall, detachable panes was also broken but
that make have been fixed.  Have you tried testing with wx 3.1?  Maybe
the wx project fixed some of these issues.

> 
> Take a peek at the Aui source code if I didn't explain the above well
> enough and it should quickly make sense.
> 
> 
> On 27/10/17 16:32, Oliver Walters wrote:
>> 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?
>>
>> On Mon, Oct 16, 2017 at 9:58 PM, hauptmech > > wrote:
>>
>> 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 tearing off the
>> AUI panels and moving them to a second monitor gave me a crucial
>> few more cm of room to view my design. These days with a 4K
>> display it doesn't seem so critical.
>>
>>
>>
>> -Hauptmech
>>
>> On 16/10/17 15:00, Oliver Walters wrote:
>>> 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 is not visible anywhere. I
>>> realize this isn't much of a problem description, but I was
>>> wondering if there was some trick that is undocumented (or
>>> documented somewhere that I haven't found it) that I need to know
>>> to display wxAUI panels.
>>>
>>>
>>>
>>> On Mon, Oct 16, 2017 at 12:29 PM, Greg Smith
>>> > wrote:
>>>
>>> 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 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
 ___
 Mailing list: https://launchpad.net/~kicad-developers
 
 Post to : kicad-developers@lists.launchpad.net
 
 Unsubscribe : https://launchpad.net/~kicad-developers
 
 More help   : https://help.launchpad.net/ListHelp
 

>>>
>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> 

Re: [Kicad-developers] wxAUI woes

[hauptmech]

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 current on kicad gui policy.  That said, everything works as I 
would expect it to.


A user with an existing config will keep that config and can use the 
pane toggle in the view menu to turn the pane on.
A new user will have an empty config file and will get the default 
config as defined in the code.


Going forward  LoadSettings() or SaveSettings() probably need a property 
filter added, as those are where SavePerspective (and LoadPerspective 
once Dick finishes per his comment in the code) are called.


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.


Take a peek at the Aui source code if I didn't explain the above well 
enough and it should quickly make sense.



On 27/10/17 16:32, Oliver Walters wrote:
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?


On Mon, Oct 16, 2017 at 9:58 PM, hauptmech > wrote:


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 tearing off the
AUI panels and moving them to a second monitor gave me a crucial
few more cm of room to view my design. These days with a 4K
display it doesn't seem so critical.



-Hauptmech

On 16/10/17 15:00, Oliver Walters wrote:

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 is not visible anywhere. I
realize this isn't much of a problem description, but I was
wondering if there was some trick that is undocumented (or
documented somewhere that I haven't found it) that I need to know
to display wxAUI panels.



On Mon, Oct 16, 2017 at 12:29 PM, Greg Smith
> wrote:

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 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
___
Mailing list: https://launchpad.net/~kicad-developers

Post to : kicad-developers@lists.launchpad.net

Unsubscribe : https://launchpad.net/~kicad-developers

More help   : https://help.launchpad.net/ListHelp






___
Mailing list:https://launchpad.net/~kicad-developers

Post to :kicad-developers@lists.launchpad.net

Unsubscribe :https://launchpad.net/~kicad-developers

More help   :https://help.launchpad.net/ListHelp





___
Mailing list: https://launchpad.net/~kicad-developers

Post to     : kicad-developers@lists.launchpad.net

Unsubscribe : https://launchpad.net/~kicad-developers

More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] wxAUI woes

[Oliver Walters]

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?

On Mon, Oct 16, 2017 at 9:58 PM, hauptmech  wrote:

> 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 tearing off the AUI panels
> and moving them to a second monitor gave me a crucial few more cm of room
> to view my design. These days with a 4K display it doesn't seem so critical.
>
>
>
> -Hauptmech
>
> On 16/10/17 15:00, Oliver Walters wrote:
>
> 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 is not visible anywhere. I realize this isn't much of a
> problem description, but I was wondering if there was some trick that is
> undocumented (or documented somewhere that I haven't found it) that I need
> to know to display wxAUI panels.
>
>
>
> On Mon, Oct 16, 2017 at 12:29 PM, Greg Smith  wrote:
>
>> 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 <
>> oliver.henry.walt...@gmail.com> wrote:
>>
>> 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
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] wxAUI woes

[hauptmech]

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 tearing off the AUI 
panels and moving them to a second monitor gave me a crucial few more cm 
of room to view my design. These days with a 4K display it doesn't seem 
so critical.




-Hauptmech

On 16/10/17 15:00, Oliver Walters wrote:

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 is not visible anywhere. I realize this 
isn't much of a problem description, but I was wondering if there was 
some trick that is undocumented (or documented somewhere that I 
haven't found it) that I need to know to display wxAUI panels.




On Mon, Oct 16, 2017 at 12:29 PM, Greg Smith > wrote:


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 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
___
Mailing list: https://launchpad.net/~kicad-developers

Post to : kicad-developers@lists.launchpad.net

Unsubscribe : https://launchpad.net/~kicad-developers

More help   : https://help.launchpad.net/ListHelp






___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] wxAUI woes

[hauptmech]

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 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 is not visible anywhere. I realize this 
isn't much of a problem description, but I was wondering if there was 
some trick that is undocumented (or documented somewhere that I 
haven't found it) that I need to know to display wxAUI panels.




On Mon, Oct 16, 2017 at 12:29 PM, Greg Smith > wrote:


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 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
___
Mailing list: https://launchpad.net/~kicad-developers

Post to : kicad-developers@lists.launchpad.net

Unsubscribe : https://launchpad.net/~kicad-developers

More help   : https://help.launchpad.net/ListHelp






___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] wxAUI woes

[Greg Smith]

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  wrote:
> 
> 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.
> class gui (layerviewset_gui.layerviewset_panel):
> """Inherits from the layerviewset_gui form wxFormBuilder. Supplies
> functions that tie the gui to the layerviewset class below."""
> _lvset_instance = None
> interior_panel = None
> def __init__(self, lvset_instance, parent_frame, pane=None, *args, **kw):
> 
> self._lvset_instance = lvset_instance
> if pane is not None:
> manager.AddPane( self, pane)
> super(gui,self).__init__(parent_frame)#, *args, **kw)
> 
> 
> Greg S.
> 
>> On Oct 15, 2017, at 9:00 PM, Oliver Walters  
>> wrote:
>> 
>> 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 is not visible anywhere. I realize this isn't much of a problem 
>> description, but I was wondering if there was some trick that is 
>> undocumented (or documented somewhere that I haven't found it) that I need 
>> to know to display wxAUI panels.
>> 
>> 
>> 
>>> On Mon, Oct 16, 2017 at 12:29 PM, Greg Smith  wrote:
>>> 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 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
 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp
 
>> 
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] wxAUI woes

[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.
class gui (layerviewset_gui.layerviewset_panel):
"""Inherits from the layerviewset_gui form wxFormBuilder. Supplies
functions that tie the gui to the layerviewset class below."""
_lvset_instance = None
interior_panel = None
def __init__(self, lvset_instance, parent_frame, pane=None, *args, **kw):

self._lvset_instance = lvset_instance
if pane is not None:
manager.AddPane( self, pane)
super(gui,self).__init__(parent_frame)#, *args, **kw)


Greg S.

> On Oct 15, 2017, at 9:00 PM, Oliver Walters  
> wrote:
> 
> 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 is not visible anywhere. I realize this isn't much of a problem 
> description, but I was wondering if there was some trick that is undocumented 
> (or documented somewhere that I haven't found it) that I need to know to 
> display wxAUI panels.
> 
> 
> 
>> On Mon, Oct 16, 2017 at 12:29 PM, Greg Smith  wrote:
>> 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 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
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>> 
> 
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] wxAUI woes

[Oliver Walters]

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 is not visible anywhere. I realize this isn't much of a
problem description, but I was wondering if there was some trick that is
undocumented (or documented somewhere that I haven't found it) that I need
to know to display wxAUI panels.



On Mon, Oct 16, 2017 at 12:29 PM, Greg Smith  wrote:

> 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  com> wrote:
>
> 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
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] wxAUI woes

[Greg Smith]

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 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
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] wxAUI woes

[Oliver Walters]

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
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp