You do not have permission to delete messages in this group
Copy link
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 build a blocks that when a button is click will go to another screen and it works, but it just stay for 5 seconds or less and go back to original page. I'm thinking that this always happening even though I debug the blockings.
TimAI2
unread,
Nov 11, 2018, 10:15:08 AM11/11/18
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
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
Please provide an image of your relevant blocks (right click on blocks editor and download image of blocks)
Use different screens wisely
Before starting to create another screen, first you should think about is it really necessary?
You do not have permission to delete messages in this group
Copy link
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
pls help need to solve this now
I was just speculating that might be the problem is the order of SCREEN but I don't think this was the issue
TimAI2
unread,
Nov 16, 2018, 6:19:09 AM11/16/18
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
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
You have several basic design problems
You are not managing switching screens correctly, this will cause memory issues and app crashes (see below)
Your "splash" screen is not the best method, as you always have the clock running, and this combined with 1 above, is causing the screen "bouncing". Do you really need to send the user back to it, once the app is started ?
You could do all of this on one screen to overcome these issues using arrangements as "virtual screens"