Programatically Detect FP Vertical/Horizontal Scrollbar Scrolling

[aderogba]

I need to be able to detect when user scrolls up/down and left/right of my VI front panel during execution. Please what are the options to accomplish this?

[Christian Mergl]

Hi,

You can use VI Server to reference the pane (This VI Ref>Frontpanel Window>Panes>take first Pane) and select the Content Area Rect Property which  coordinates values are changing when scrolling up/down and left/right.

Christian

[Broken_Arrow]

For a handy boolean indication that a scroll took place....

Message Edited by Broken Arrow on 11-10-2009 12:13 PM

[Broken_Arrow · Accepted solution]

sorry about the deleted imbedded picture. Trying to stop imbedding pictures from Gallery. Lets try again....

Message Edited by Broken Arrow on 11-12-2009 08:07 AM

[MinerHokieRamp]

Replying to a related post because I don't see a 'new message' button.

I'm trying to use the "key repeat?" event to move the FP horizontal crollbar box with left and right arrow keys; prefer that to repeatedly pushing the keys. However, it seems that events are stored after the limits are reached and with event discarded. It takes a while to reverse scrolling, seems like many events are stored beyond the limits. I don't have a grasp of what's going on with this event.

Appreciate any help you can provide to help me understand this event and how to constrain panel scrolling and reverse scrolling direction without delay. Example code (LV 2014 home/student edition) is attached.

Thanks,

[GerdW]

Hi Ramp,

when you want to have immediate reaction of your VI you should not use a wait function in your loop!

Because of the "key repeat" event you will always have a small delay: there's a deley between initial key stroke and the first key repeat.

And it would help to have the origin cluster wired through ALL event cases. "Default if unwired" tunnels can enforce unwanted behavior of your VI…

[MinerHokieRamp]

---

@GerdW wrote:

Hi Ramp,

when you want to have immediate reaction of your VI you should not use a wait function in your loop!

Because of the "key repeat" event you will always have a small delay: there's a deley between initial key stroke and the first key repeat.

And it would help to have the origin cluster wired through ALL event cases. "Default if unwired" tunnels can enforce unwanted behavior of your VI…

---

Changing the value of the input to the wait function eliminated the problem. I tried removing it but it scrolled too fast so I brought it back and set it to about 20 ms.

The wait function was a leftover from when I first tried a 'key down' event for scrolling.

Thanks,