> I'll need more details about both of your questions. Right now I don't have
>enough to come up with an answer.
Amazing :)
> Question 1: What object is defined in what resource? Where are you
>"activating" it and how?
>
> Question 2: Please indicate which objects/methods/functions are running
>under what threads. What do you want to do with the threads in Swat?
I have a background application that just waits idle and minds its own
business.. until some other application sends it a message.
App works in its own process thread. Then it must tell results to the user,
who might be using whatever application doing whatever whenever. Therefore
I go to system ui thread and bring up a dialog there == visible everywhere.
This dialog does not block, it just stays on top and waits. My app might
receive more messages, the other apps do whatever, things have to go on
all the time. User might not notice the dialog for hours/days/weeks.
No problem, it's done - with max two (2) triggers.
The problem is that the dialog must have three (3) triggers. One brings
up another dialog, which must be scrollable, after which we return back
to the first dialog.
Best guess is to go to system ui thread and there duplicate a resource
defined in my own app and activate it == bring on-screen. But where do
I connect it, how do I activate it.. I could easily have it as part of
my own app's object tree and INTERACTION_INITIATE within system thread,
but I believe it would be run in my app's process thread. Correct? Can
I have separate object tree/branch not connected anywhere and just call
it's root object with MSG_GEN_INTERACTION_INITIATE?
After that the third trigger is no problem. Problem is how to scroll in
system ui thread, but this is a minor matter - at the moment.
Now you have some more details. Any suggestions before I go and do the
system described above? If nothing else works, I use my app's process
thread and block the whole system during these dialogs (there are more,
but they are no problem == max two (2) triggers).
Ahem.. of course the perfect solution would be a more usable function
from Geoworks, one that would allow me to define all four (4) triggers.
FoamStandardDialogOptrNoBlock();
I'll have to dig into .defs and .gohs and check how UserStandardDialog()
is used with GIT_MULTIPLE_RESPONSE and if that could be used :(
>Nathan
--jouni