When I started on Qt, I found that I didn't need to stray any further than the Qt Assistant doco to learn how things work. You need to spend time reading the doco, it's VERY important. Work through the tutorials contained in the doco as well.
When I started on Qt, I found that I didn't need to stray any further than the Qt Assistant doco to learn how things work. You need to spend time reading the doco, it's VERY important. Work through the tutorials contained in the doco as well.
Yes ... you are right.
I was in "kind of a hurry" but i guess i definitely need some reading
Thanks all .... "I'll be back"![]()
Ok then.
I've been trough the The Direct Approach, The Single Inheritance Approach and The Multiple Inheritance Approach.
Guess that each one as it's own application filed.
The third one seems more comfortable to use, although it says that "...but does not conveniently support composition of multiple user interfaces".
When i use Qt Creator to start a project based on QDialog class (for instance) it uses single inheritance ... right!
Can i ask why? Is it because of what i said above, and this way the template will cover all situations?
Hope this is not another stupid question![]()
Bookmarks