> In a nutshell, when a lot of events fire in rapid succession, the > user-interface locks up. >
I can't really replicate your problem since I'm responding to these on a Mac. But the event structure has a Boolean checkbox for Locking the UI during the processing. This makes sense for UI events, and may sometimes make sense for User Events. Look for a way to turn off the UI locking during the processing of the events. Of course this may also be caused by the ActiveX control needing to run in the UI thread, and it may be difficult to tell the difference except to experiment with them. Because the diagram still responds, I expect it to be the locking. As for the handles, most LV allocations aren't tracked in the performance monitor. Since the handles are cleared up when the VI goes idle, I suspect that it is the cleanup/garbage collection of LV that is closing ActiveX references that are being opened and never closed. You might look around in the reentrant VI or other code in your app for ActiveX references that may need to be closed explicitly on your diagrams. If the handles didn't return at idle, it might be more indicative of a bug in LV. > Anyone seen anything like this? > Anyone (NI guys) have any ideas? > Follow up question (NI guys): when will the support for the old > ActiveX event stuff dry up? > I'd say the dry-up date has something to do with when you and other users find that the new stuff totally eclipses it. Greg McKaskle
