How to avoid built-up for "cursor move" events?

[carloman]

Hello All,

This example is elegant, and serves as one of the better examples Ive found on events in that it covers the issue of events being queued.

I'd like to extend this a little further, and not send any data once the knob has stopped moving...ie: to only send data when the slide is moving, and then stop once the knob stops.

I can think of various ways to do this: analyze the selective output stream using shift regs and block the output once it "flat lines" or perhaps add another loop inside the case to unblock once out output(selective) starts changing again.

Could someone suggest how to implement this extension ? Im working on it but as a newbie, its a bit of a leap at this stage.

Thanks,

Carlo

ps: Ive added a value change event to detect changes in the Selective output, and pass them on...but I get no response. Can anyone see whats wrong ?

Message Edited by carloman on 05-08-2007 08:25 PM

[carloman]

Heres the edited vi...didnt load last time.

[parthabe]

This seems to be a very good learning material about Graph Cursor events, without LV 8.2...

I dont know when my boss will give the go ahead to buy 8.21.

Maybe after LV 9 gets released in Nov 2007 here in India.

[titi_nicolas]

carloman, you must use the property node "value (signaling)" in order to trigger the value change event!

[altenbach]

---

@carloman wrote:
Heres the edited vi...didnt load last time.

---

Please don't mutilate my original perfect example and repost it containing only my name on the front panel!!

This is very bad manners. I have nothing to do with your modification, so please add appropriate comments that my original example was modified by you.

Also add comments about what you did and why.

... and why would you replace my control with such an ugly knob?

[carloman]

Hello altenbach,

Im sorry that my post may give that impression. I agree that your example is indeed excellent and said so earlier. I thought that the flow of threads would make it clear that it was my change, but I did not think of adding extra comments on the diagram. (Actually I was concerned to avoid taking any credit for the example, and thought my change would be evident...my mistake).  It is something i will think of doing in future posts.

There are many subtleties on the learning curve for LV which are hard to pick up from Help, so this forum serves a good purpose for newbies to LV and posting.

Any further help would be appreciated.

Regards,

Carlo

[carloman]

Hi Titi,

Thanks for your suggestion.

I'm not clear on value signalling vs. local variable, but in any case, after a few variations, my latest attempt is still not working.

I have documented my aims on the attached block diagram, and I'm sure there is a simple way to achieve this mod.

Basically, I'd like a knob which only transmits data when moved....and theres a few ways to achieve this...however the LV syntax escapes me so far.

Any suggestions much appreciated.

Carlo

[altenbach]

Whatever you are trying to do makes abbsolutely no sense. It is a nonissue. Since the main even only executes when the value changes, the purpose is already met in the original code. Maybe I misunderstand.

[carloman]

Yes, I see what you mean. I had the impression that the last value was continually output, but the main detection loop does only output changes.

Using the "lightbulb" feature helped make this evident to me.

Hi ho, hi ho, its up the learning curve I go......

Thanks,

Carlo

[altenbach]

Yes, I went through all that song and dance with the third loop and all these ugly local variables just to be able to graphically record what is going on with the immediate state of each variable. The upper loops definitely only spin as needed and that's all you need in typical code. 🙂

Good luck!