Unregistered
December 7, 2002, 07:26:50
We just spent HOURS trying to figure out why the windows close button (X), stopped sending its message.
The scenario is this, a dot net SDI application using multiple tabs created run time each with a TX Control. Today we added the close function, and found if we closed even one tab, we no longer got any msg from the windows close button. It just stopped working.
We had done a similar app back in April with TX in net interop (v8.1), and had no problem.
Apparently (???) in anything other than an MDI, you may need to specifically dispose of any TX controls. Adding m_ActiveTX.Dispose() to our DocumentClose() resolved things for us. (If we use TX on any modal dlgs, we'll probably call the Dispose there as well, just for safe measure.)
This message was originally posted by Vann Joe in the old TX Text Control Support Forum.
The scenario is this, a dot net SDI application using multiple tabs created run time each with a TX Control. Today we added the close function, and found if we closed even one tab, we no longer got any msg from the windows close button. It just stopped working.
We had done a similar app back in April with TX in net interop (v8.1), and had no problem.
Apparently (???) in anything other than an MDI, you may need to specifically dispose of any TX controls. Adding m_ActiveTX.Dispose() to our DocumentClose() resolved things for us. (If we use TX on any modal dlgs, we'll probably call the Dispose there as well, just for safe measure.)
This message was originally posted by Vann Joe in the old TX Text Control Support Forum.