Quote Originally Posted by wysota View Post
Resources are compiled into the binary and occupy the memory all the time.
Really? I thought there is a way to unload them and free the memory. Q_CLEANUP_RESOURCE()? I never tried that.

Quote Originally Posted by wysota View Post
Hmm... so how do you want to access the data from code if it is only to be available to the automated code? Or maybe I don't understand what you mean by "gui creation" - for me setupUi() does that.
Ah yes, I really don't meant gui creation, but hmm, how do I call it...interface dispatch? All in all I am trying to find a better way to give classes a better way to access the designer generated objects. The designer is a fine tool, I just think the way its code has to be connected to the main program code sucks.

Quote Originally Posted by wysota View Post
So it does the same qFindChildren() does, only on the separate object hierarchy, right?
Actually yes, the returned object should be different. Else if you want to keep the method to encode hierarchy informations in the object name, you probably could even use qFindChildren the way it is now. But I don't think this 'reuse' would be good.

Quote Originally Posted by wysota View Post
But then you could only use it in a class generated by Designer.
This I don't understand. Why?

Quote Originally Posted by wysota View Post
According to me the thing you want is a nice candidate for a completely separate component that can be implemented using Qt but not necessarily inside Qt.
I am thinking how I could create such a component. I think I could create a wrapper around designer generated classes, which implements parts of the interface I described. But all depends on hierarchy information somewhere in the designer created objects. I might be willing to swallow the bitter pill and parse the object names, but then I had to set them manually. And this makes IMHO all the work pointless.