You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to MIT App Inventor Forum
That feature is not available in AppInventor 2 (perform click)
Suggest you ask in the appinventor distribution you are using....
For what it is worth, it is probably due to you asking too much of screen initialise, not enough time to do everything, you may need to introduce a clock timer between setting the source and playing
Taifun
unread,
Feb 6, 2019, 10:33:17 AM2/6/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to MIT App Inventor Forum
I set When Screen1 Initialize do "Call Station1 .Perform click" but the click is not performed when screen is initialized.
put the blocks from the Station1.Click event into a procedure and call that procedure in the Screen.Initialiize event as well as in the Station1.Click event
also make sure to switch screens correctly, see tip 1
App Inventor works best if you use images whose size matches the size you want them to appear on your screen. If you import larger images into your app, your app may run out of system memory. Using Images with App Inventor
by Italo: First, you need to understand that the file size of an image is not the amount of memory it uses when it's being displayed. The file size is the compressed size, much like a zip or rar file. When viewed, the image needs to be decompressed.
For example, if your image says its file size is 100 kb, and its dimensions are 1024 x 768, 32 bit color, then that image uses over 3 mb of RAM (not 100 kb!) when you show it on the screen. ((1024 * 768 ) * 32) / 8 = 3,145,728 kb (3 mb)
Now, this is a mistake most people make when using arrangements as "virtual screens": They set different image components with their images loaded but hidden, instead of having only one image component and changing the picture according to the user's selection or app events, not knowing that apparently the hidden image components are also using the ram, (yes, even though they are invisible!).