Yes thats another action! Key is not Mouse. When there is key focus on the control i handle this with the Key Down? filter event and it works perfect. But Mouse down is different. You don't get the information if one hit the up/down arrow, thus you can't filter this like with key down?
Yes of course I do use the event structure. I tried the rollaround thing but there is one major bug in this idea. What if one, selecting from the list that comes up when u hit the ring control, wants to select the last item while the current selection is at the first item?! Then this trap won't let the user select the last item and vice versa. And I have no idea how to handle this.
Second idea is possible but i have like more than 100 rings in my applications and I have to support like 20-30 applications all over. I don't like the idea to have additional 200 up/down controls in my app just for this little feature. I mean you can enter limits and coerce them. But it seems to be a problem for NI to implement this feature to stop at the lower/upper end, or they just don't see the needs to implement this to LV.
Best regards
Stocki