Please Help, I Can't get the Screen1 Initialize to perform a button click

88 views
Skip to first unread message

Legendary Apps

unread,
Feb 6, 2019, 6:04:54 AM2/6/19
to MIT App Inventor Forum
Please Help, I set When Screen1 Initialize do "Call Station1 .Perform click" but the click is not performed when screen is initialized.

It is a radio app and I want the station to play once launched without manual clicking of the play button. 

"Please zoom the image to see the Block on the far right-hand side"
blocks.png

TimAI2

unread,
Feb 6, 2019, 6:54:57 AM2/6/19
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
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

  1. Use different screens wisely
    Before starting to create another screen, first you should think about is it really necessary? See also Building apps with many screens and SteveJG's post about advantages/disadvantagesbecause in only one screen you also can use vertical arrangements to simulate different screens, just set the arrangements to visible = true/false as needed... See also Martyn_HK's example about how to use Tabs in App Inventor and another example from Cyd

    If you decided to use different screens, then you should switch them correctly, else you will run out of memory after a while...      
    The recommended method of switching screens in App Inventor

  2. 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!).

  3. Avoid redundancy
    Probably it helps to read chapter 19 - 21 in Dave's book http://www.appinventor.org/book2 to get an idea how to do DRY programming with App Inventor - Don't repeat yourself 

  4. See SteveJG's monster list of tips and tricks

  5. How to overcome the App Inventor project limit of 10 MB

  6. Backup your project frequently
Taifun

Trying to push the limits of App Inventor! SnippetsTutorials and Extensions from Pura Vida Apps by  Taifun. 


Reply all
Reply to author
Forward
0 new messages