P
pswulius
Hey everyone,
for reasons I can't explain quickly, I'm developing a completely custom
OK/OK_CANCEL dialog, though I think many people would benifit from this
knowledge. I basically need to re-invent the wheel and provide a
simple API like:
Result result = CustomDialog.Show( Mode.OK_CANCEL, aMessage );
The problem that I'm not sure how to solve is the blocking aspect that
dialogs I've used in the past offer. Obviously I'd like to invoke this
line of code from various points in my application and have it block
until user input is received.
Does anyone have experience with this type of problem? I think I need
a way to "hand-off" processing to a secondary GUI thread, or something
like that. Especially since this dialog will arise as a result of user
interaction with the main UI.
Any and all advice would be great. The solution may not be available
from a high-level C# api, but I still wanted to post here. Thanks.
--pete
for reasons I can't explain quickly, I'm developing a completely custom
OK/OK_CANCEL dialog, though I think many people would benifit from this
knowledge. I basically need to re-invent the wheel and provide a
simple API like:
Result result = CustomDialog.Show( Mode.OK_CANCEL, aMessage );
The problem that I'm not sure how to solve is the blocking aspect that
dialogs I've used in the past offer. Obviously I'd like to invoke this
line of code from various points in my application and have it block
until user input is received.
Does anyone have experience with this type of problem? I think I need
a way to "hand-off" processing to a secondary GUI thread, or something
like that. Especially since this dialog will arise as a result of user
interaction with the main UI.
Any and all advice would be great. The solution may not be available
from a high-level C# api, but I still wanted to post here. Thanks.
--pete