Recent changes to bugs

Error thrown for empty cluster arrays.

James Cook — Thu, 17 Jun 2010 13:56:03 -0000

In LabVIEW, auto-indexed for loops don't execute when the input array is empty. In this case, all tunnel outputs will pass out their default values, and all shift register outputs will pass out their input values.

On 6/17/2010, Jon (http://lavag.org/user/17719-jhow88/) reported an error that relates to this standard functionality in a forum post (http://lavag.org/topic/10976-a-mat-file-io-library/page__view__findpost__p__75283).

It turns out that there were several instances where a for loop was used to process array elements recursively, but tunnels were used to pass the recursive VI reference through the for loop. When the input array was empty, the output VI reference would be invalid. The invalid reference would pass into the close reference VI, which would throw the error that Jon reported.

The fix is easy. Just replace all of the tunnels that pass VI references with shift registers. Then if the input array is empty, the output VI reference will be the same as the input VI reference, and there will be no error thrown.

Only the first element of Nx1 double arrays is read in.

James Cook — Tue, 29 Sep 2009 12:21:18 -0000

1D double arrays are always read in as 1xN arrays. Therefore, when a Nx1 array is read in, only the first element will be returned to the user instead of the full 1D array. This bug might be present when reading 1D logical, cell, and struct arrays also.

This bug was reported here: http://lavag.org/topic/10976-a-mat-file-io-library/page__view__findpost__p__66584

"Anything" VI doesn't properly write array of clusters

James Cook — Mon, 28 Sep 2009 11:50:50 -0000

This was reported here: http://lavag.org/topic/10976-a-mat-file-io-library/page__view__findpost__p__66263

Element ordering problem with struct arrays greater than 1D.

James Cook — Tue, 22 Sep 2009 10:13:40 -0000

The order of elements is not correct in struct arrays with 2 dimensions or more. 1D structs and single-element structs are not affected by this bug.

Error in writing char arrays.

James Cook — Thu, 17 Sep 2009 14:57:08 -0000

There was a problem writing character arrays. The variable name was not being written in the proper way.

Problem with strings containing ASCII code 128..255 chars.

James Cook — Tue, 15 Sep 2009 17:53:39 -0000

Strings that contain characters between ASCII code 128 and 255 are not written properly.

Extract Data Element (1D Struct) only handles 1x1 structs.

James Cook — Fri, 11 Sep 2009 15:56:24 -0000

Only a 1x1 struct is handled properly by "Extract Data Element (1D Array of Data Element from 1D Array of Struct).vi". If the struct is a 1xN, then only the fields of the first element are returned by the VI.