Unnamed phenomenon?

Bugs and Other Issues
1

I open up a browser, go to AI2, select a project, connect to the companion, and voila, um, er, only half the app comes up on my device. Hmm.
To debug, I remove every from from the initialization block, reconnect, and step through each step, including subroutines, individually using right click and Do it. This way the app works as it should, everything appears on the device screen and operates within normal parameters. So, resetting everything, I reconnect, and alas! half the app is missing again until I debug by "Do it"ing each step individually.... grr
What is this paranormal phenomena known as?

(Windows 10, latest Firefox and Cat S62 Android 11)

2

  1. Is this on your haunted chromebook ? :wink: - ah you just posted on Windows 10

  2. Companion on a smartphone or tablet, not the Android app on the Chromebook ?

  3. Show your relevant blocks in Screen1.Initialise

  4. Which browser ?

  5. Can you repeat behaviour with an example project ?

3

I've stopped using my chromebook, I guess it's old enough that the poltergeists tempt the limitations of my medication... :crazy_face:
I reinstalled the companion on on my device, removed all coded formatting from the blocks and am now formatting using the designer. it seems to have improved a little. (I am confused though as to why the compiled version still runs on my device with no issue)
I am guessing that any percentage in height or width is of the screen and NOT the parent, correct? I am having to keep a scratch pad and calculator handy...

4

Yes, percentages for height and width are based off Screen height and width, once they have initialised (which may not be in the screen initialise block)

What do you mean by the parent ?

5

How does one confirm initialization?
Parent is the view holding something, eg, vertical arrangement would be the parent to any controls placed within it.
So a button set to 50% wide would be 50 of the screen and NOT the arrangement, even if the arrangement was set to 25%. The button therefore would be twice the size of the arrangement it is in. Correct?

6
  1. If you are settings heights and widths against the Screen height and width, it is best practice to use a clock timer with an interval of, say, 200msecs, and do the settings in there. This should give time enough for the screen to get its own height and width.
  2. Yes
7

so, left unchecked, its moving faster than it's legs can carry it.... and therefore we need to build in some wait time for each screen to draw itself before moving on.
Gotcha, that makes sense.
Thanks Tim

p.s.
thanks for the clarity on percentages. It solves other issues too. :ghost: