Nasty bug with tables (LV 8.2)

[Jaegen]

This seems to be a very simple but nasty bug.  Maybe it's just something to do with my PC/installation.

Run the attached VI, and while it's running click inside any cell in the table (WARNING: this crashes LV on my PC, so save and close any work first).

I get a fatal internal error: "transact.cpp", line 1323

Jaegen

P.S. this has been reported to NI via the automatic internal error investigation system

[Will.D]

Confirmed on my machine (8.2 as well)

[BrianInTheForest]

same here using LabVIEW 8.20 on win2k.

[Jaegen]

Some further info:

• Sorry, in my shock I forgot to mention that I'm running Windows 2000 - can anyone confirm this in XP?
• "LV82TableBug03.vi" pares it down to the basics - even if the data being written to the indicator isn't changing, it still crashes
• "LV82TableBug04.vi" shows that it happens when writing to a local variable of a table control, but only if the control has key focus when it's actually written to (i.e. you can click in and out of the table in between writes without a crash).  When it does crash the behaviour is strange - on my PC it will keep running for some time, but if I click or move the mouse, it usually crashes (I can't figure out the details)
• "LV82TableBug05.vi" demonstrates what should be the best work-around, but I'm still able to crash it sometimes (not repeatable - it probably requires clicking on the table after the property node is read but before the indicator is written), and it prevents the rest of the table from being updated while the table has key focus.

Since the work-around isn't reliable, this bug pretty much prevents the user from easily copying text from a cell of any table that's being periodically updated - Ouch.

Jaegen

[Joe_H]

Confirmed,

LV 8.20 win XP

This bug almost makes tables useless, also another thing I noticed it is just clicking in the cell on y machine you had to move the mouse after clicking inside the cell.

NI needs to give us a patch for this. NOW would be good.

[Jaegen]

---

NI needs to give us a patch for this. NOW would be good.

---

Amen

[decyL]

and all was light... ;-]

amen

[JeffBoettcher]

I'm sorry I don't have a fix for you now, but I thought I'd at least let you know that this was reported to R&D (41I6CPA4) for further investigation.

[pbparker]

Anyone know if any patch has been made available for this problem yet?

[Joe_H]

There will probably not be a patch put out. It might get fixed in the next version of LV.