DaveKielpinski Posted January 8, 2008 Report Share Posted January 8, 2008 Unlike normal event structures, XControls have the odd behavior that you can register them for User Events, but firing a User Event doesn't wake up the XControl. There are a couple possible workarounds, including using a daemon VI to monitor for User Event firing. The new workaround is really simple: just add empty event cases to the XControl, such that any stimulus that fires a User Event also fires the empty event case. If the User Event comes from an actual user interface event, it's easy to find the right event for the empty case. I'm not sure whether the weird XControl behavior could be fixed in a future version, or whether it might qualify as a bug. It sure would be a lot more intuitive if the User Event would just wake up the XControl! There were some old threads about this already (e.g. http://forums.lavag.org/Dynamically-regist...15&p=40302) but I wanted to pull it together. Best, Dave Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.