Outstanding.. I not expect such a quick answer!
No, its a Qt application. I carry out only for structural reasons. Do I need a custom event dispatcher in this case too?
Outstanding.. I not expect such a quick answer!
No, its a Qt application. I carry out only for structural reasons. Do I need a custom event dispatcher in this case too?
Lol... thanks
No, in that case just make sure you have a QApplication object in the application and don't create any static widgets or pixmaps. If you create those all objects on request, everything will work just fine (after all Qt itself is a set of libraries as well).No, its a Qt application. I carry out only for structural reasons. Do I need a custom event dispatcher in this case too?
hmm... as you note the term 'static' somewhat rings somewhere...
I'm afraid my 'clever' 'object-factory' is not really clever: its only a sample but I was curios about creating widgets wich I only know at runtime..
hmm.
so far, thanks a lot wysota. I'll have a look. I let you and the others know about this issue
<info>
hmm, actually, it seems this behaviour appears only if I link against the Qt-debug libs (e.g. QtCored4.lib). No idea why.
</info>
Solution: My mistake was that I linked against another dll wich was created in release configuration. (typical newbie-bug I think)
>> Mod: you can delete this thread if you want.
Last edited by montuno; 10th March 2008 at 16:19. Reason: updated contents
Bookmarks