Using both dialogs and "windowed" (that sucks sorry) windows on a app, in other words having a dlgprog and a windowproc in the same app is in any way not recommendable? I ask this because thats how my app looks like now, keep in mind in a beginner :) I got two message queues, is that heavy for a normal app?
So what would you say? Am i slowing down my app unnecessarily? Should i just get everything into a rc file and go with dialogs? That kindda confused me when i started this project cause i didnt know how would i gettext/settext from editfields and getstate/setstate from checkboxes without having HWNDS for the controls (using the rc file).
Now i feel like ill have lost less time, mainly with creating the tab controls and its behavior (man, that got me crazy).
Whats your opinion?
Thanks in advance!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Using both dialogs and "windowed" (that sucks sorry) windows on a app, in other words having a dlgprog and a windowproc in the same app is in any way not recommendable? I ask this because thats how my app looks like now, keep in mind in a beginner :) I got two message queues, is that heavy for a normal app?
So what would you say? Am i slowing down my app unnecessarily? Should i just get everything into a rc file and go with dialogs? That kindda confused me when i started this project cause i didnt know how would i gettext/settext from editfields and getstate/setstate from checkboxes without having HWNDS for the controls (using the rc file).
Now i feel like ill have lost less time, mainly with creating the tab controls and its behavior (man, that got me crazy).
Whats your opinion?
Thanks in advance!