Type of Application

[sweep123]

This is a general question. I am about to start a larger project which will result in lots of dialog windows providing operator input, selections and outputs.
Would like the user to have control of what windows are on display - resize keep on top etc.
Also would like, if possible have some of the windows still visible when the application is minimised.
I have used modeless dialogs, but was thinking about MDI and user threads.
Basically what I would like to do is have some of these (modeless dialogs?) visible while swithing to another application, resize the other application and generally manage the window area for the job in hand.
So was planning to use Visual Studio .Net (C++) MFC Dialog application with modeless dialog windows (perhaps with user threads on some of these dialog windows).
Any comments before I go down this route.

Sweep.

 

[PerFnurt]

In general I would recommend that you have only 1 GUI thread in your application.


/Per

_{if (typos) cout << &quot;My fingers are faster than my brain. Sorry for the typos.&quot;;}

 

[palbano]

>> lots of dialog windows providing operator input,
>> selections and outputs.

Could you possibly use another approach? Personally i hate applications that throw a multitude of dialogs at me.

>> Would like the user to have control of what windows are on display - resize keep on top etc.

If you use a standard Window whenever possible the UI can be more intuitive and flexible.

Take some time and really work on the UI design and layouts. Get some external input if at all possible. Think about using splitter windows, list controls and tabbed windows to reduce the shear number of top level windows where ever possible. Integrate the UI whenever it makes sense.

&quot;But, that's just my opinion... I could be wrong.&quot;

-pete

 

[sweep123]

I get the impression that to have dialogs always on display (when the user selects this option) to be a bt difficult.

Several Tabbed dialogs may be the best option.

Thanks for your input.