I've been searching the forums, and I find them referencing substring stuff on other boards, but not specifically anything for AppGameKit, and I've searched the help files for everything involving strings, and maybe it's just not easily recognizable? I've searched google, but that doesn't seem to turn anything up either. My reasoning for this is that if I have a number, it's far easier to convert it to a string, then step through each string character index, converting each individual character back to a number to display a score. I'm sure I can write a function to display the score, but it would be infinitely easier with a substring method.
I did experiment with text objects for displaying of numerical data, however, what looks perfect at declared resolution on my computer, looks horrendous on my mobile. Even though I apply the same modifiers to size, and position coords as I apply to my sprites to keep them exactly as I want them (size and position) regardless of window size, the text objects are 4 to 5 times the size they should be, and the text is not as clear at the size I need it to be on the mobile device. So I'm using sprites to display numerical data, which allows me to display very clear numbers in the space I have to display them, with the added bonus that my sprites don't do wild things when the window is resized, or the platform changes. (yes I'm using virtual display, and not using percentages with my size or location data.)
So if anyone could point me toward commands that would permit me to access a string characters by an index, ie "Hello World!" = 0,1,2,3,4,5,6,7,8,9,10,11 I would greatly appreciate it.
Currently I'm thinking of a function similar to the following if there aren't any valid string methods.
temp = score
ten = 0
hun = 0
tho = 0
tentho = 0
huntho = 0
if temp > 999
while temp > 999
temp = temp - 1000
tho = tho + 1
endwhile
if temp > 99
while temp > 99
temp = temp - 100
hun = hun + 1
endwhile
etc...
endif
endif
Which will work in a roundabout fashion, but what I don't like about it is that it's going to be checking from what is likely going to be a very big number, and it's 5 lines of code per place.