When maximizing and then restoring a pane, the layout of the panes
after the maximize/restore is different than the layout before. See
attached screenshots: first the tree pane is at the bottom left
(aui1), but after maximizing (aui2) and restoring it, it is at the
middle left (aui3).
The screenshots were made with the pyAUI version in wxPython 2.8.10.1
on Windows XP. However, I see this issue also with Task Coach, which
is using a fairly recent version of pyAUI from SVN (updated two weeks
ago or so). I see this issue also with the regular AUI included in
wxPython 2.8.10.1.
I tried to look for a bug in the pyAUI code, but no luck so far. Any
hints where to dig further?
When maximizing and then restoring a pane, the layout of the panes
after the maximize/restore is different than the layout before. See
attached screenshots: first the tree pane is at the bottom left
(aui1), but after maximizing (aui2) and restoring it, it is at the
middle left (aui3).
The screenshots were made with the pyAUI version in wxPython 2.8.10.1
on Windows XP. However, I see this issue also with Task Coach, which
is using a fairly recent version of pyAUI from SVN (updated two weeks
ago or so). I see this issue also with the regular AUI included in
wxPython 2.8.10.1.
I tried to look for a bug in the pyAUI code, but no luck so far. Any
hints where to dig further?
There was a problem like this some time ago Sept/Oct time frame (see thread "pyAUI - RestoreMinimized problem". As far as I can see it is fixed for me here - I am on SVN version for AGW widgets.
BTW, the default start up perspective layout is different for me, i.e. just the tree pane on the left. If I show all panes then it is on the left in the middle, but in both cases min/max/restore seem to behave correctly for me.
When maximizing and then restoring a pane, the layout of the panes
after the maximize/restore is different than the layout before. See
attached screenshots: first the tree pane is at the bottom left
(aui1), but after maximizing (aui2) and restoring it, it is at the
middle left (aui3).
The screenshots were made with the pyAUI version in wxPython 2.8.10.1
on Windows XP. However, I see this issue also with Task Coach, which
is using a fairly recent version of pyAUI from SVN (updated two weeks
ago or so). I see this issue also with the regular AUI included in
wxPython 2.8.10.1.
It's a bug in PyAUI, I can reproduce it on my GTK VM (unfortunately I
can't test on Windows right now (!!!!!!) as my new machine is a 64 bit
one and I always get an assertion error using timers with PyAUI: this
bug should be solved by the next release of wxPython).
I tried to look for a bug in the pyAUI code, but no luck so far. Any
hints where to dig further?
The issue arises when restoring the pane from a maximized state
(obviously): it could possibly be an issue in the UpdateLastKnownDock
method, as this method sets a dock row, layer and direction but not a
position inside the dock (not sure though about this, Michael H may be
more helpful on this part of the code). I don't currently have much
time to dig into this (I'll be on holiday up to the 4th of January,
and I prefer to be with my family than fixing code ). Other than
that, I believe Michael H is more expert than me in this specific part
of the code (maximizing/restoring panes), so if he can jump in with
some suggestions it would be a great help for me too. Otherwise, I'll
try to take a look at it if I can get some time in the next few days.
If you come up with a patch, it would be most helpful...
When maximizing and then restoring a pane, the layout of the panes
after the maximize/restore is different than the layout before. See
attached screenshots: first the tree pane is at the bottom left
(aui1), but after maximizing (aui2) and restoring it, it is at the
middle left (aui3).
The screenshots were made with the pyAUI version in wxPython 2.8.10.1
on Windows XP. However, I see this issue also with Task Coach, which
is using a fairly recent version of pyAUI from SVN (updated two weeks
ago or so). I see this issue also with the regular AUI included in
wxPython 2.8.10.1.
It's a bug in PyAUI, I can reproduce it on my GTK VM (unfortunately I
can't test on Windows right now (!!!!!!) as my new machine is a 64 bit
one and I always get an assertion error using timers with PyAUI: this
bug should be solved by the next release of wxPython).
I tried to look for a bug in the pyAUI code, but no luck so far. Any
hints where to dig further?
The issue arises when restoring the pane from a maximized state
(obviously): it could possibly be an issue in the UpdateLastKnownDock
method, as this method sets a dock row, layer and direction but not a
position inside the dock (not sure though about this, Michael H may be
more helpful on this part of the code). I don't currently have much
time to dig into this (I'll be on holiday up to the 4th of January,
and I prefer to be with my family than fixing code ). Other than
that, I believe Michael H is more expert than me in this specific part
of the code (maximizing/restoring panes), so if he can jump in with
some suggestions it would be a great help for me too. Otherwise, I'll
try to take a look at it if I can get some time in the next few days.
If you come up with a patch, it would be most helpful...
BTW, I see the same issue with wx.aui. If you can't manage to find a
solution to this, and if Michael H doesn't step in, please create a
bug report for both agw.aui and wx.aui on the bug tracker. so that it
doesn't get lost.
In the meantime I think you should be able to avoid the problem if you use the 32-bit version of Python/wxPython.
···
On 12/29/09 2:02 PM, Andrea Gavana wrote:
It's a bug in PyAUI, I can reproduce it on my GTK VM (unfortunately I
can't test on Windows right now (!!!!!!) as my new machine is a 64 bit
one and I always get an assertion error using timers with PyAUI: this
bug should be solved by the next release of wxPython).
I will take a look at this now... sorry for the delay..
holidays..
- michael
···
On Dec 29 2009, 4:36 pm, Robin Dunn <ro...@alldunn.com> wrote:
On 12/29/09 2:02 PM, Andrea Gavana wrote:
> It's a bug in PyAUI, I can reproduce it on my GTK VM (unfortunately I
> can't test on Windows right now (!!!!!!) as my new machine is a 64 bit
> one and I always get an assertion error using timers with PyAUI: this
> bug should be solved by the next release of wxPython).
In the meantime I think you should be able to avoid the problem if you
use the 32-bit version of Python/wxPython.
--
Robin Dunn
Software Craftsmanhttp://wxPython.org
any further problems after he applies it let me know..
- michael
···
On Jan 2, 10:28 am, michael h <michaelke...@gmail.com> wrote:
I will take a look at this now... sorry for the delay..
holidays..
- michael
On Dec 29 2009, 4:36 pm, Robin Dunn <ro...@alldunn.com> wrote:
> On 12/29/09 2:02 PM, Andrea Gavana wrote:
> > It's a bug in PyAUI, I can reproduce it on my GTK VM (unfortunately I
> > can't test on Windows right now (!!!!!!) as my new machine is a 64 bit
> > one and I always get an assertion error using timers with PyAUI: this
> > bug should be solved by the next release of wxPython).
> In the meantime I think you should be able to avoid the problem if you
> use the 32-bit version of Python/wxPython.
> --
> Robin Dunn
> Software Craftsmanhttp://wxPython.org
). Other than