So now in the Forum
There is only one native array available, it was discovered by user indev2 random typings.
the b[.id].attribute component array allows access by .id number for component in a page.
b in theory would be the current page as the Page Component is always .id of 0
b would be the first component on the page with .id attribute 1
the last component has an .id attribute equal to component count
So in this b[.id] Component Array all attributes are accessible. And this is good and bad.
For a Number component n0 with id 5 then b.val is equivalent to n0.val
- but b.txt is also not a compile error even though n0 does not have a .txt attribute
it will however, create a runtime error and program logic fails.
page4.b.val is the third component on page name page4 - great for accessing globals.
- but you really need to know that what you are calling is an attribute that truly exists
therefore if I have global string variable components in id positions 1 to 12,
then I can use it very naturally for month names
If id 13 to 20 also were global string variable components containing weekday names
then t1.txt=page0.b[rtc6+13].txt // rtc6 value+an offset
The weekday names is 13 to 20 as Sunday needs to be both 13 and 20 depending if RTC6 is 0 or 7
So this b[.id].attribute native array allows things to shorten a fair amount
IF you take the time to specifically and purposely arrange your components