[Qt-interest] Basic non modal dialog question
John McClurkin
jwm at nei.nih.gov
Wed Feb 17 13:50:24 CET 2010
Phil wrote:
> Again, thank you for reading this.
>
> My application's main window class causes a non modal dialog to be
> displayed that looks to the user (me) to be a secondary main window. This
> dialog is always shown and displays data that are periodically sent from the
> application class. Like all classes in my application the display dialog class
> can receive data from the application class and return data, but only if it is
> interrogated. None of the slave classes have knowledge of each other or are
> able to initiate contact with the application class.
>
> So, how is the application class made aware that the user has entered data
> into the dialog class? Should the dialog class not be a separate class itself
> but instead belong (if that's the correct term) to the application class? That
> way the normal signal / slot mechanism can be used and that seems to be
> the only answer. I don't think signals and slots work across classes.
??!! Of course signals and slots work across classes. Also work across
threads. Now if you are really talking about processes, you need to look
at some type of interprocess communication system like COM on Windows or
DBus on linux.
More information about the Qt-interest-old
mailing list