Comparing with the Your sample Apps is not real fair: in Your samples, You create 1,2 or 3 dialogs, not more. In the real world, I have to create 20 up to 40 dialogs. I’m also not sure, how to find out, where the runtime is wasted. Measuring the time to switch between dialogs is very hard. So my fisrt try is to find out, what code need a lot of time, in my try: Open an existing document, create all needed dialogs and display at screen.
a) I started with only a very little Prof-UIS elements (old version): 1.1 sec
b) replaced all CDialog with CExtResizableDialog: 1.8 sec
c) For each element used CExtLabel, CExtEdit, ... (BUT NOT CExtComboBox): 3.6 sec
d) like c) but now also used ( about 70) CExtComboBox: 5.7 sec
So, it seems, that CExtComboBox needs so much time. Done a cross-check:
e) No CExtResizableDialog, No CExtLabel, CExtEdit, only CExtComboBo: 2.6 sec
From substrcatime time of c) from time of d) and adding base time of a) I would exspect a time of e) 3.7 sec.
So, it seems to me, that ist is very important, how much Prof-UIS elements are called. And this is only an example, I have a lot of documents with lot of different dialogs. The time measurement was done during lod of document, without any timers running, no idle processing, omly very few command update code.
Waht do I wrong? Where can I speed up?
TIA
Willi
P.S. Tnx, I know the SetAutoSubclassChildControls API, but for finding out the time consumption, I do not use it. I have tried, I get exact same timeing, when using this function instead of declaring and calling by hand