VI of the Day (10/16/2009) - Set Cursor VI

[Darin.K]

Another off-the-wall VI for Friday, "Set Cursor.vi".  This one has some practical uses as well, when I remember it, I use it when I am running a long calculation.  Of course, you have to be careful because cursor changes can often lead to shortness of breath and blood rushing to your head, as well as the occasional profane outburst that gets you in trouble.  Personally, I have lost many writing utensils and have spewed caffeinated beverages on more than one keyboard and monitor.

Like most stressful events, the endorphin rush afterwards can be fun.  To relive the cause of much stress during grad school I have written this simple VI to bring back an old friend from my Mac days on LV 2/3.  I still get a twitch when I see this cursor.

VIOTD groundrules here. 

[RavensFan]

Cool VI.

Try this one (I couldn't save it below LV 9.0 because LV crashed.)  It uses an event structure and makes the changes to the cursor whenever you change the control without having to restart.

[Darin.K]

---

Ravens Fan wrote:

Cool VI.

Try this one (I couldn't save it below LV 9.0 because LV crashed.)  It uses an event structure and makes the changes to the cursor whenever you change the control without having to restart.

---

It is not just me then, LV2009 seems to be crashing an inordinate number of times for me when I try to save for previous.  I tend to write my examples in LV8.6 to avoid the hassle.

[Ben]

Back saving code with event structures from LV 2009 to anything other than LV 8.6 is a known bug.

Work-arounds

Save to 8.6 and use it to go fartehr.

replace teh vent with a stacked seq, back-save and convert the event structure again.

The bug has been reported and a little birdy said R&D has this bug figured.

Ben

[elset191]

What is that cursor?  It looks like a snow plow and a street sweeper.

[Darin.K]

That was the infamous Bulldozer of Doom.  It seemed to reflect some form of garbage collection which always seemed to end badly.

[RavensFan]

---

Darin.K wrote:

It is not just me then, LV2009 seems to be crashing an inordinate number of times for me when I try to save for previous.  I tend to write my examples in LV8.6 to avoid the hassle.

---

Nope, not just you.  I had read a couple threads about this issue.  This was the first I had seen it myself.

The projects I'm working on are still in LV 8.6, I haven't upgraded them to LV 9 yet.  (By the way, I just installed the 2009f2 patch yesterday.)  But I tend to have LV 2009 open when I browse through the forums so I can see any code that is posted.

I have had some weird error messages with LV8.6.  Sometimes on opening LV8.6, I get an investigate previous error (I haven't documented the exact error, but investigating it turns up nothing (does it ever?))  However, I don't remember having any crashes in LV8.6 when I used it last.  And there is never any files to be auto-recovered.  Basically, I didn't have an error, but LV thinks it did when it reopens.

Next time this happens, perhaps I'll post the message and see if anyone else has had this issue.  I basically not tell it not to investigate, and LV8.6 opens fine and I proceed with my work.

[Ben]

---

Ravens Fan wrote:

...

I have had some weird error messages with LV8.6.  ...

---

If you look in

...My Documents\LabVIEW Data\lvfailurelog

you will find a time stamped txt file that records the error you see.

Inside that file it also gives a clue as to which version di dthe crashing.

Ben

[RavensFan]

I hadn't paid close attention to that bug.  Thanks Ben for pointing out that it is tied into the event structure.  Makes you wonder why that bug would not present itself in the LV9 to 8.6 back save, but would for older back saves.  Especially considering LV 8.6 didn't seem to have problems going back 3 versions to LV8.

For completeness, here is the link to where the bug is reported.