I'm back now, so I can answer all the questions
1) Qt works exactly the same way
2) dynamic cast is not needed as the component designer knows the class name, so there is no point of using dynamic cast because you can't access pimpl from outside the class anyway.
3) dynamic_cast relies on RTTI from the compiler, so you'd want to avoid that if possible.
That was because some things may not work, so I didn't want to see comments like "X doesn't work" - I already know it doesn't workAny other comments on unstable widgets are welcome.
The navigation bar is stable, the problem with it is that you can't use its Designer plugin correctly, because of a major bug in Qt.but I had some minor success yesterday hacking the qwwnavigationbar component into some sort of stability.
Sure, let's have a lookI've got the primary functionality working with the PushButtons activating the correct QWidget in the top half of the splitter and have sucessfully "styled" the PushButtons to the original "Outlook" (silver version) look similar to my screen grab above but without the minimize bar. The question is if you want the code fed back - I've changed both the header (replacing the topButton with a QLabel) and cpp and have added pngs to the resource file. Any interest?. I don't think you have to add any images to the resource file, as CSS capabilities from Qt should allow you to make use of external images. About the button in the header - you can access the button and disable its "clicking" functionality if you don't like it without modifying the actual class (or you can subclass of course).
You should have run "nmake install" after the compilation. The dll needs to be present in both the lib directory (so that you can make use of the component from your applications) and in the bin directory (so that Designer can access it). Furthermore you should have the file "wwwidgets4plugin.dll" available as well and it should land in your plugins/designer folder (nmake install should take care of that).
Well... you should have received a .so file if you didn't stick any "static" keywords during preconfiguration. I'll have a look at the project file to see what might have gone wrong and I'll get back to you on that.
Bookmarks