i get a list error saying attempt to get list value from item of length 0. this error does not happen in the compiled app on the phone only during the development phase. there is no indication in which block it happens and i tried to disable all relevant blocks and cannot pin it down.
any suggestions? that prevents me to perform decent development because the error pops up every 5 sec
i thought i take care of this in the screen initialize block where i fill the empty list with '0'.
should this not take care of it?
also i did not get this error before so i thought i made some changes that would explain it but cannot find a problem.
and also this error does not seem to affect the runtime behavior
sorry i will try to do better but it takes me quite a bit of time to condense the code down this much.
btw what is the best method to use only one screen - there is no screen extract function so i assume just deleting all the excess screen is the way to do it.
there is no trick how the debugger can point me to a block where the message comes from?
also when i disable a block is that going into effect right away or do i need to reset connection and reconnect to the phone?
sorry lot's of questions you probably answered already millions of times.
what i am trying first is compare to an older version where this problem did not show up
in the motiontrack.initialize
the list was never generated because it was after the
file1.scope and
file.append statement
so the add.items to list loop was never executed because the program jumped out of the block and then the list was length 0 - makes sense.
once i move the add.item loop to the top (just BEFORE the file stuff) all worked.'
also because of the file1.scope block
i get in the development environment the run time error
'item is neither class nor type'
but this shows up only once and all is ok
to ABG's question
you are right that is a questionable code and i took it out.
the purpose was that i tried to preserve the data in case the INITIALIZE is done again when i leave the app and come back but that does not work either i guess, so you are right - was a bad idea.
all this file stuff in android 11 is still a black box to me but at least now i can continue in the development environment with out the pop up error.
we need better debugging and break points.
so thanks again and i am really sorry you had to crawl through my code - not nice i know.
i am not sure how i can support your work, where do i donate?
but i hope my 2 hour debug activity and explanation also helps you a little
ABG, i updated the companion and now the error
'item is neither class nor type'
is gone
thanks for the suggestion - i forgot about this because i did turn automatic update off