I’ve found a nasty bug in Juce - a fast fix would be really appreciated.
Create an app with tabbed-based interfaces (I’ve got two different apps that both do this…)
i.e. based on MultiDocumentPanel …
Start the app, add a tab
Close one of the tabs - it doesn’t matter which one - the remaining revealed tabbed Window
displays blank (!) though the tab itself is OK; press that tab to the underlying component
to be repained properly!
… simply resizing the container window doesn’t cause the ‘revealed’ tabbed Component to
repaint (!!)
Just checking to see if you’ve pushed this to the repo or not - the most recent commit I can see in master is 3 Jun 2013 - “WASPI: used mix format channel mask.” (14ec53de2e5d7e493c973ac0a2b91a8fb912e170)
Once I can pull it, I’ll be very happy to test it for you.
You need to use the new git URL
git clone --depth 1 git://github.com/julianstorer/JUCE.git
and Sourceforge RSS if you use it http://sourceforge.net/p/juce/code/feed
I’ve pulled-down the very latest code from the latest repo … and have stepped through your changes to TabbedButtonBar::removeTab (just to verify that your code changes were pulled-in properly) … but the problem remains.
Let me know if there is anything I can check from my side!
Well, I reproduced it in the juce demo widgets page, and fixed it there. If you can give me some test-case code that still fails, I’ll take another look!
OK, that gives me some serious hacking around to do, in order to create a test case for you, I guess!
The problem might be related to FileBasedDocument based apps that are based on multi-document panels - which the Jucer Demo isn’t, of course?
Have you got any internal test-bed apps that work like that? It is going to take a lot of work otherwise to get a stripped-down test app for you to build with.