Dear cup319,
It is more than a wonderful example. Very well done. I will try it with a screen reader by adding bigger cycle values for example 50 what Android accessibility Suite Talkback will report when swiping. But I Am wondering about your approach because of a very important fact. That it is clear, that It is really not necessary to specify object position values by using DIP numbers. I will test it and I have a last plea to you, dear MR cup319.
Could you also add little code which would react on some button click so show message could for example display "you have clicked on button number", variable name
After that, I will be finally able to build my loving preverb test. I have 45 Czech preverbs and it is necessary to complete The end of every incomplete preverb. I will be very happy because B4A generates a very¨memory efficient app which can run even on my old Samsung GT-B5330 with 160 MB free RAM because the Talkback screen reader and Espeak speech engine allocate for example 50 or more MB of RAM. So thank you again and I Am telling you. Very well done and thank you. I have given it up working with B4A because I have thought, that without position values of objects I will be lost forever. But thanks to your useful programmers' tip, I will return to B4A back.