From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
04-10-2019 06:42 AM
I made a couple of posts here about scrollwheels on arrays. Its a different use case but you can probably still use the "delta" from the event data to achieve what you need.
Have a play with and see what you can come up with 🙂
0xDEAD
04-10-2019 09:37 AM
04-10-2019 09:39 AM
Just a reminder to be careful with the "in range" function's default limits: upper limit is not included lower limit is..
04-10-2019 10:02 AM - edited 04-10-2019 10:02 AM
@crabman wrote:
Just a reminder to be careful with the "in range" function's default limits: upper limit is not included lower limit is..
Yes, its a good point to remember! Black diamond indicates included, open diamond is not. They are settable in the right click context menus.
0xDEAD
04-10-2019 10:49 AM
09-02-2022 02:46 AM
This is still an issue in 21.0.1f2. It just really bit me badly.
One of the benefits of the built-in mouse wheel support is changing the increment based on the position of the cursor, I can not find a way to do this without the built-in mouse-wheel support.
09-03-2022 12:41 PM
@Wiznilly wrote:
This is still an issue in 21.0.1f2. It just really bit me badly.
One of the benefits of the built-in mouse wheel support is changing the increment based on the position of the cursor, I can not find a way to do this without the built-in mouse-wheel support.
If this is still a problem (not tested), you can easily detect a rollover in software and act accordingly before the rest of the code sees it.
09-04-2022 06:07 PM
Altenbach,
Thanks for the response. My post was intended to just (re-)report the issue, but now that you mention the workaround... here is what I have considered:
Let's say that my limits are 1-100, I put a hard limit on the absolute difference between the old and new values and just ignore anything that is greater than half the range (50). Is there a better way?