Weirdness with COLUMNNAMES() function

[tnorvell]

Quick bug/unexpected issue with the COLUMNNAMES() function. I noticed that the number of columns can't be less than the size of the array. For example:

dim option$(5,2)

' load the option$() array with whatever
' you want here.
'

table #menu, option$()
#menu columnnames("Column1,Column2,Column3")
render #menu
wait


This will cause a nasty runbasic error until the dim option$(5,2) command is changed to (2,2) so that it matches the number of columnnames specified. I would have figured that if fewer columns were specified the extra array elements would be ignored.

[Alyce]

runbasic.wikispaces.com/Table

ColumnNames

A special row called a header is placed at the top of the table. It contains the names of the columns if the ColumnNames() statement is issued. Remember that the number of columns is equal to the number of elements in the second dimension of the array, which is 0-indexed. This array has four columns: DIM Array$(3,10).

ColumnNames are added as a string expression, delimited by commas. The array we've created might use this statement to name the columns, 0,1,2,3.


#handle columnnames("First, Second, Third, Fourth")