The latest changes to auibook.py (revision 63896) have introduced a
bug into one of my applications. I have an AuiNotebook that contains
a page that also contains an AuiNotebook. If I click into the page
with a nested notebook using the latest revision, none of tabs are
clickable in the nested notebook, and the mouse is never released.
A couple other bugs I'd like to point out that are visible in the
demo:
1. In the AUI portion of the wxPython demo, if you click the close
button on the "Welcome to AUI" tab, and then proceed to click yes in
the dialog that pops up, the application hangs. I presume this is
because the next tab over is disabled. If you remove the line in the
code that makes the tab disabled or shuffle the "Welcome tab to the
right of the disabled tab before closing it, it works fine.
2. In the code for AUI demo, comment out the line that disables the
2nd tab in the main notebook, for me it's line 2066 (ctrl.EnableTab(1,
False)).
Now, launch the demo with the changes. Under the "Notebook" menu,
click "Allow Single Tab Floating." Next, close every tab EXCEPT for
the "Welcome to AUI" tab. Lastly, click the tab and drag it to the
left just far enough for the tab to float and release. You'll notice
that the contents of the tab's page are still in the notebook. Now
move the floating tab around and you'll see the contents of the
floating frame "burned-in" to the notebook, which has not refreshed.
The latest changes to auibook.py (revision 63896) have introduced a
bug into one of my applications. I have an AuiNotebook that contains
a page that also contains an AuiNotebook. If I click into the page
with a nested notebook using the latest revision, none of tabs are
clickable in the nested notebook, and the mouse is never released.
Yes, I have seen that today, I have just committed a small change to
fix this (plus some other small improvements to framemanager and ULC).
A couple other bugs I'd like to point out that are visible in the
demo:
1. In the AUI portion of the wxPython demo, if you click the close
button on the "Welcome to AUI" tab, and then proceed to click yes in
the dialog that pops up, the application hangs. I presume this is
because the next tab over is disabled. If you remove the line in the
code that makes the tab disabled or shuffle the "Welcome tab to the
right of the disabled tab before closing it, it works fine.
Correct, it is because of that. I'll hunt it down to correct it as
soon as I get some time.
2. In the code for AUI demo, comment out the line that disables the
2nd tab in the main notebook, for me it's line 2066 (ctrl.EnableTab(1,
False)).
Now, launch the demo with the changes. Under the "Notebook" menu,
click "Allow Single Tab Floating." Next, close every tab EXCEPT for
the "Welcome to AUI" tab. Lastly, click the tab and drag it to the
left just far enough for the tab to float and release. You'll notice
that the contents of the tab's page are still in the notebook. Now
move the floating tab around and you'll see the contents of the
floating frame "burned-in" to the notebook, which has not refreshed.
Yep, I can see that too. Please enter a bug report for these 2 issues
together so that your report does not get lost.
A couple other bugs I'd like to point out that are visible in the
demo:
1. In the AUI portion of the wxPython demo, if you click the close
button on the "Welcome to AUI" tab, and then proceed to click yes in
the dialog that pops up, the application hangs. I presume this is
because the next tab over is disabled. If you remove the line in the
code that makes the tab disabled or shuffle the "Welcome tab to the
right of the disabled tab before closing it, it works fine.
It should be fixed now.
2. In the code for AUI demo, comment out the line that disables the
2nd tab in the main notebook, for me it's line 2066 (ctrl.EnableTab(1,
False)).
Now, launch the demo with the changes. Under the "Notebook" menu,
click "Allow Single Tab Floating." Next, close every tab EXCEPT for
the "Welcome to AUI" tab. Lastly, click the tab and drag it to the
left just far enough for the tab to float and release. You'll notice
that the contents of the tab's page are still in the notebook. Now
move the floating tab around and you'll see the contents of the
floating frame "burned-in" to the notebook, which has not refreshed.