Re: Message Loops

2010-10-14 Thread Matt Siebert
Agreed. The thing is, in this scenario, the client in the other process will provide a very rich GUI. By passing the window handle from my form in the native app's process to my GUI in it's own process, I can set my GUI's parent window appropriately so that clicking the native app's main window a

Re: Message Loops

2010-10-14 Thread noonie
Matt, Go with the second option if you need to block the GUI. Hiding this sort of stuff from users in almost never a good idea. Most users will accept an informed wait time over an apparently hung app. -- noonie On 15 October 2010 13:34, Matt Siebert wrote: > Bugger. As I suspected the orig

RE: Message Loops

2010-10-14 Thread Ben.Robbins
otnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Matt Siebert Sent: Friday, 15 October 2010 10:35 AM To: ozDotNet Subject: Re: Message Loops Bugger. As I suspected the original call from the client is blocked so re-entrant call

Re: Message Loops

2010-10-14 Thread Richard Mason
>>> you can't do that, then a modal form sounds like a good idea to me >>> because >>> if you are blocking the native app, then you should provide a cancel >>> button >>> etc. >>> >>> >>> |-Original Message-

Re: Message Loops

2010-10-14 Thread Matt Siebert
27;t do that, then a modal form sounds like a good idea to me because >> if you are blocking the native app, then you should provide a cancel >> button >> etc. >> >> >> |-Original Message- >> |From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet- &g

Re: Message Loops

2010-10-14 Thread Matt Siebert
u are blocking the native app, then you should provide a cancel button > etc. > > > |-Original Message- > |From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet- > |boun...@ozdotnet.com] On Behalf Of Matt Siebert > |Sent: Friday, 15 October 2010 1:44 AM > |To: ozDotNet

RE: Message Loops

2010-10-14 Thread Bill McCarthy
ea to me because if you are blocking the native app, then you should provide a cancel button etc. |-Original Message- |From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet- |boun...@ozdotnet.com] On Behalf Of Matt Siebert |Sent: Friday, 15 October 2010 1:44 AM |To: ozDotNet |Subject: Me

Re: Message Loops

2010-10-14 Thread Matt Siebert
hibited. If you have received this e-mail in > error please contact the sender immediately and then delete the message and > any attachment(s). > > > > > > *From:* ozdotnet-boun...@ozdotnet.com [mailto: > ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Matt Siebert > *S

Re: Message Loops

2010-10-14 Thread David Richards
Have you tried opennet? I seem to recall using something similar in opennetcf. ApplicationEx I think. As a word of warning though, I discovered issues with click events (and presumeably any event) being fired during the transition. ie, the events would be lost when I was returning from the new m

RE: Message Loops

2010-10-14 Thread Mitch Denny
f Matt Siebert Sent: Friday, 15 October 2010 1:44 AM To: ozDotNet Subject: Message Loops G'day folks, Aside from Application.Run() and Form.ShowDialog(), are there any other ways to run a message loop in a .NET app? I'm not keen on rolling my own message loop, I'm just wondering if th

Message Loops

2010-10-14 Thread Matt Siebert
G'day folks, Aside from Application.Run() and Form.ShowDialog(), are there any other ways to run a message loop in a .NET app? I'm not keen on rolling my own message loop, I'm just wondering if there are other options already available. Why do I want to do this? Well I'm developing an add-in fo