Modeless dialog issue
-
I don't have anything in any of the handlers. It has pretty much nothing in it. I put one button on it that doesn't do anything. (I was just testing). The only code in it is the
public ChatMessageForm() { InitializeComponent(); }In this case, source code is the only thing that will help us solve your problem. This includes the code surrounding your chatMessageForm.Show() method.
If my answer has helped you, one of my articles may also be a help. Also remember that your best friend's name is google.
-
In this case, source code is the only thing that will help us solve your problem. This includes the code surrounding your chatMessageForm.Show() method.
If my answer has helped you, one of my articles may also be a help. Also remember that your best friend's name is google.
Well the code looks a bit like this.....
public partial class ChatMessageForm : Form { public ChatMessageForm() { InitializeComponent(); } }private void ProcessChatMessageEvent() { ChatMessageForm c = new ChatMessageForm(); c.Show(); }ProcessChatMessageEvent is called by.....public void OnEvent(Object sender, EventPublisher.EventPublisherEventArgs eventArgs) { EventID nReceivedEvent = (EventID)eventArgs.iEventID; switch (nReceivedEvent) { case EventID.eChatMessageEvent: ProcessChatMessageEvent(); break; } }I checked and it works properly outside of the switch which kinda amazes me. (The OnEvent is a Cisco event handler) -
I am trying to pop up a modeless dialog box using .Show() It does pop up the dialog, but it freezes and the components never load. I can open the same dialog with .ShowDialog() and it loads properly. But that doesn't accomplish what I am looking for in the dialog because i need it to be modeless. So, is there something that I am missing to make show work correctly? It is a pretty simple out of the box dialog that I am testing with, just from VS2008 designer with one button on it.
The difference between
ShowandShowDialogis that the first method displays the form and continues with the next line of code, while the second method pauses execution of the code until after the form has been closed. Observe:MyForm F = new MyForm();
F.ShowDialog();
System.Diagnostics.Debug.WriteLine("Output");In this case, the string Output will not be written to the Immediate window until the pop-up form is closed. If you replace
F.ShowDialog()withF.Show(), Output will probably be written before the form finishes rendering. I suspect that your calling code needs to wait until the dialog has been handled, which is whyShowDialogworks andShowdoes not. This can be a real pain if you are writing a MDI application, as child windows cannot be invoked withShowDialog. Added: After looking at the code you posted above, I can see the problem. After callingShow(), the method ends. The variable referencing your form goes out of scope and gets recycled: your form is not getting a chance to render before it gets disposed. If it absolutely has to be modeless, you will need to move the scope of your form's variable out. -
Well the code looks a bit like this.....
public partial class ChatMessageForm : Form { public ChatMessageForm() { InitializeComponent(); } }private void ProcessChatMessageEvent() { ChatMessageForm c = new ChatMessageForm(); c.Show(); }ProcessChatMessageEvent is called by.....public void OnEvent(Object sender, EventPublisher.EventPublisherEventArgs eventArgs) { EventID nReceivedEvent = (EventID)eventArgs.iEventID; switch (nReceivedEvent) { case EventID.eChatMessageEvent: ProcessChatMessageEvent(); break; } }I checked and it works properly outside of the switch which kinda amazes me. (The OnEvent is a Cisco event handler)aei_totten wrote:
works properly outside of the switch
Hmm, so your saying that the following code would work:
public void OnEvent(Object sender, EventPublisher.EventPublisherEventArgs eventArgs)
{
//EventID nReceivedEvent = (EventID)eventArgs.iEventID;
//switch (nReceivedEvent)
//{
//case EventID.eChatMessageEvent:ProcessChatMessageEvent();
//break;
//}
}If my answer has helped you, one of my articles may also be a help. Also remember that your best friend's name is google.
-
The difference between
ShowandShowDialogis that the first method displays the form and continues with the next line of code, while the second method pauses execution of the code until after the form has been closed. Observe:MyForm F = new MyForm();
F.ShowDialog();
System.Diagnostics.Debug.WriteLine("Output");In this case, the string Output will not be written to the Immediate window until the pop-up form is closed. If you replace
F.ShowDialog()withF.Show(), Output will probably be written before the form finishes rendering. I suspect that your calling code needs to wait until the dialog has been handled, which is whyShowDialogworks andShowdoes not. This can be a real pain if you are writing a MDI application, as child windows cannot be invoked withShowDialog. Added: After looking at the code you posted above, I can see the problem. After callingShow(), the method ends. The variable referencing your form goes out of scope and gets recycled: your form is not getting a chance to render before it gets disposed. If it absolutely has to be modeless, you will need to move the scope of your form's variable out.Gregory.Gadow wrote:
Added: After looking at the code you posted above, I can see the problem. After calling Show(), the method ends. The variable referencing your form goes out of scope and gets recycled: your form is not getting a chance to render before it gets disposed. If it absolutely has to be modeless, you will need to move the scope of your form's variable out.
Now, that makes sense. However, in the real application, I have more demands of that form (I just wanted to get a simple one working first because I was running into this issue and couldn't pin point it). Here's some code....
private Dictionary<string, ChatMessageForm> chatMessages = new Dictionary<string, ChatMessageForm>(); ... string message, sender; message = "blah"; sender = "me"; if (!chatMessages.ContainsKey(sender)) { chatMessages.Add(sender, new ChatMessageForm(sender)); } chatMessages[sender].ShowDialog();}The Dictionary is declared outside of the process in the scope of the main form. However, i do think the issue is related. This is my first time using Dictionary so maybe I am missing something there... -
aei_totten wrote:
works properly outside of the switch
Hmm, so your saying that the following code would work:
public void OnEvent(Object sender, EventPublisher.EventPublisherEventArgs eventArgs)
{
//EventID nReceivedEvent = (EventID)eventArgs.iEventID;
//switch (nReceivedEvent)
//{
//case EventID.eChatMessageEvent:ProcessChatMessageEvent();
//break;
//}
}If my answer has helped you, one of my articles may also be a help. Also remember that your best friend's name is google.
Richard Blythe wrote:
Hmm, so your saying that the following code would work:
yes
-
The difference between
ShowandShowDialogis that the first method displays the form and continues with the next line of code, while the second method pauses execution of the code until after the form has been closed. Observe:MyForm F = new MyForm();
F.ShowDialog();
System.Diagnostics.Debug.WriteLine("Output");In this case, the string Output will not be written to the Immediate window until the pop-up form is closed. If you replace
F.ShowDialog()withF.Show(), Output will probably be written before the form finishes rendering. I suspect that your calling code needs to wait until the dialog has been handled, which is whyShowDialogworks andShowdoes not. This can be a real pain if you are writing a MDI application, as child windows cannot be invoked withShowDialog. Added: After looking at the code you posted above, I can see the problem. After callingShow(), the method ends. The variable referencing your form goes out of scope and gets recycled: your form is not getting a chance to render before it gets disposed. If it absolutely has to be modeless, you will need to move the scope of your form's variable out.Found out something else. Even without the Dictionary, just moving the declaration of the Form out into the scope of the main form was not enough to fix the problem
-
Richard Blythe wrote:
Hmm, so your saying that the following code would work:
yes
well crud. I can't even reproduce that today :(
-
Found out something else. Even without the Dictionary, just moving the declaration of the Form out into the scope of the main form was not enough to fix the problem
Based on your last post, it seems that you need to look into the Cisco event behavior. For example, a standard windows event will not give you this behavior. Try trapping an event from your main form like this:
//...
public frmMain()
{
InitializeComponent();
frmMain.Click += new EventHandler(frmMain_Click);
}ChatForm frmChat;
void frmMain_Click(object sender, EventArgs e)
{
if (frmChat == null)
{
frmChat = new ChatForm();
frmChat.Show();
}
frmChat.BringToFront();
}If this works without a hitch (which it should), then you should contact Cisco and report a bug! :)
If my answer has helped you, one of my articles may also be a help. Also remember that your best friend's name is google.
-
Based on your last post, it seems that you need to look into the Cisco event behavior. For example, a standard windows event will not give you this behavior. Try trapping an event from your main form like this:
//...
public frmMain()
{
InitializeComponent();
frmMain.Click += new EventHandler(frmMain_Click);
}ChatForm frmChat;
void frmMain_Click(object sender, EventArgs e)
{
if (frmChat == null)
{
frmChat = new ChatForm();
frmChat.Show();
}
frmChat.BringToFront();
}If this works without a hitch (which it should), then you should contact Cisco and report a bug! :)
If my answer has helped you, one of my articles may also be a help. Also remember that your best friend's name is google.
Thanks for the relpy. It does work fine from a button event or other main form generated event. However, I created a System.Timers.Timer and called the method from it's elapsed event handler and that created the same freeze as seen from the Cisco event handler.
-
Thanks for the relpy. It does work fine from a button event or other main form generated event. However, I created a System.Timers.Timer and called the method from it's elapsed event handler and that created the same freeze as seen from the Cisco event handler.
Okay, maybe it's a thread issue. Most of my apps doesn't required thread sensitive code. Try using thread context code like this:
//Cisco event handler (can't rem it's method def)
...
{
InvokeMethod();
}private delegate void EmptyHandler();
private void InvokeMethod()
{
if (this.InvokeRequired) // 'this' is frmMain
this.Invoke(new EmptyHandler(InvokeMethod), null);
else
{
ChatForm frmChat = new ChatForm();
frmChat.Show();
}
}This create the new chat for on the same thread as the main form. Maybe a long shot, but it may be what your looking for... Cheers, Richard
If my answer has helped you, one of my articles may also be a help. Also remember that your best friend's name is google.
-
Okay, maybe it's a thread issue. Most of my apps doesn't required thread sensitive code. Try using thread context code like this:
//Cisco event handler (can't rem it's method def)
...
{
InvokeMethod();
}private delegate void EmptyHandler();
private void InvokeMethod()
{
if (this.InvokeRequired) // 'this' is frmMain
this.Invoke(new EmptyHandler(InvokeMethod), null);
else
{
ChatForm frmChat = new ChatForm();
frmChat.Show();
}
}This create the new chat for on the same thread as the main form. Maybe a long shot, but it may be what your looking for... Cheers, Richard
If my answer has helped you, one of my articles may also be a help. Also remember that your best friend's name is google.
That did it. I had tried previously checking if the dialog needed invoke but i didn't check this.invokerequired Thanks so much!
-
That did it. I had tried previously checking if the dialog needed invoke but i didn't check this.invokerequired Thanks so much!
Great! I was a pro and didn't even know it. :laugh: Maybe you'll have the answer for me when I need it.
If my answer has helped you, one of my articles may also be a help. Also remember that your best friend's name is google.