Delete From Array Ghost Row?

[Jonnie_5]

In LV 7, if I wire a 2D array to Delete From Array and delete the entire array (e.g. a 2x2 woth 2 rows deleted), the output is a 0 by X array where X is the original array column size. How can that be? This is not a problem in LV 6i. Similar weirdness occurs with Replace Array Subset. Ideas? Insanity? Examples attached in both versions.

LV 7 / WinXP

[Ankita]

Hi Jonnie,

I could reproduce the behavior you reported about Delete From Array VI in LV 7.0 and 7.1.1. It works fine in LV 6.1 though. This definitely looks like a bug and I have reporetd it to R&D so they can investigate it further.

I have not been able to reproduce the problem with Replace Array Subset however. It would be great if you could explain it a bit more/post a VI.

Thanks for reporting the faulty behavior.

Ankita
National Instruments

[Jonnie_5]

Hmmm, now I can't seem to replicate the replace array issue...

Strange that what once worked... now does not.

However, if you want to make more ghosties you can use a For loop (this has been a bug for a long time):)

[chilly_charly]

And if you transpose the empty array inside the loop you get a splendid 5x5 array, filled with zero values...
I would like to get such behaviour with beer bottles : when empty, shake for a while and... hooooo, there is some more in !

CC

[altenbach]

---

@chilly charly wrote:
And if you transpose the empty array inside the loop you get a splendid 5x5 array, filled with zero values...
I would like to get such behaviour with beer bottles : when empty, shake for a while and... hooooo, there is some more in !

CC

---

The proper analogy would be that you shake the empty crate and it fills with empty beer bottle 😞
(Still not too shabby with todays redemption values for recycled bottles :))

[Jonnie_5]

Fortunately I live in michigan, so I can actually reap those benifits 😛

Anyone know of a listing anywhere of all the known bugs (and possible workarounds) for LV bugs? Digging through the forums can be a chore.

This one's annoying, but insane objects and hot wire errors are a real bugger.
~j5

[Ankita]

This is really weird. I am more concerned with the outpur array being filled with zero values than with the returned array size though that is wrong too. Anyway, thanks for reporting the bug. I will report this to R&D as well.

Ankita
National Instruments

[Mache]

J5~

Ni Could easily do that as part of forum or their website. But they dont do it... Guess Why not?

But the Bug List is available on Lava Forum. It may not be complete but atleast it is there...

http://forums.lavausergroup.org/index.php?s=ae00218c8e4f4d43b177963aa457ac85&showforum=17

[InfiniteNothing]

This appears to still be in LabVIEW. Is this still intended behavior.

To reproduce: Create a 2D array that's 1x4 delete the 1 row, use build array to add a 1D array with 2 elements, the result is a 1x4 array 

[InfiniteNothing]

Screenshot (running LV2009)