Variables window

[olzeke51]

eval of the '812, ARMBasic 9.33b, [kernel 8.33 I do believe] - variables window from the BT tools tab
playing around with DIM blah(nn) as STRING & DIM stuff(nn) as BYTE
WHEN I did add the 'as BYTE' and played with it -- I got the corruption that I highlighted <---issue #1
***
initially - I had the 'as BYTE' after the 'as STRING' but it still showed up on the top of the display -like the picture;; LATER I moved the 'as BYTE' as the first DIM'd statement and it didn't change the view in the window - okay - I can live with it
***
issue#2 --> the 'as BYTE' array doesn't show all my data UNLESS I declare it as at least 64 (if I remember correctly)
I know that a (15) or (16) will not show but more than the two groups of hex characters
**
I've tried to arrange the picture to show the program working, no errors running or loading, as well as the bulk of the program
**
in the bigger program that I loaded and ran - I was attempting to clear the string memory but I used the "$" instead of 'as STRING'
is that an issue?? ALSO I did not assign any data to the string - I assumed it would zero it like a common variable. ??good assumpt??
**
PS. will the variables window be available in the Multi-Core Basic Tools??

[olzeke51]

first time I ran it on a BasicChip - I got the same display of variables,
garbage after the name , and a short display of the BYTE data.

[basicchip]

The memory dumps treat BYTE and STRING as the same thing, and what you see there is the 09 and 0B ASCII characters, which on a PC are graphic things.

[olzeke51]

here is some more info on the display of the variables - the length , the layout , the amount of info is the issue
this is on the BasicChip - I changed the DIM values as indicated in the RED annotations

[olzeke51]

maybe I misunderstood you -- the data inside the quotes is a display of the first few characters of the actual data ???
OKAY -- just changed the first few bytes of ShortMessage and got a good display of the ASCII data I put in there.
but there is stil the issue of AMOUNT of display -- the MSSG array isn't showing me the "f"[HEX] of the 15th element
AND if you display the first 3 character in the quotes - then MSSG should have " 1" as 31 hex is ascii 1.

[basicchip]

Strings are terminated by a 0, so anything after that 0 won't be displayed inside the quotes.