Voluntarily removed How to track debug process?
-
EDITED / ADDENDUM
Here is a small B&W ( bells and whistles ) twist.
I am going to let the user "close" the unneeded debug child subwindow and write a code to "automatically " re rille " the mdiArea.
If the main debug window is NOT derived as mdiArea subwindow then the user could not have an option to restore the "closed" main debug window.
I am a firm believer that coding and debugging the project should be done currently.
End of story.Here is my philosophy in action.
My project main GUI window is mdiArea.
Whenever feasible , each subwindow has it own , child window which keeps tabs on tracking and debugging processes.
As one benefit , the user has a choice to keep or hide the stuff I do during development..I would like to extend this debugging and tracking and have another , main subwindow to track ALL subwindow - kind of dupe.
My silly question
should this top level window be a main application object or be as another child mdiArea subwindow?I am planning to use Qt "connect" to pass necessary info from real subwindow to its tracking child window
I could just extend "connect" to this main tracking window..
Are there any "gotcha " or advantages as far as the main tracking window "parent " ?
Or does it make beans difference ?
Your opinion, please.
-
@AnneRanch said in How to track debug process?:
should this top level window be a main application object or be as another child mdiArea subwindow?
With the context provided, it is not possible to answer this question, or even brainstorm about it.
It's unclear, how this question relates to the headline of your post.
