Using Multiple Screens


#1

I hope anyone can help me…
I read a lot that its not a good idea to use more screens because of memory issues…

But when i have made an app with many blocks in one screen i always get compile errors…

now my question is: is it better to fill one screen with all the blocks or is better than to split the blocks on two or more screens?

and… are these compile errors only when i make the app with app inventor or will it also the same problem if i make the same stuff for example with android studio? (if i learn Java :D)

Sorry for my bad english… i hope you understand what i mean…


#2

Hi Guenter:

Having a lot of blocks shouldn’t be a problem. Can you show the compile errors you get?


#3

I will… next time when i am on my laptop…
its an error in the activity stage…

no red or yellow warnings… no empty sockets… less procedures… less if blocks… i always try to use the any component stuff… no images or soundfiles… small apk size…

as i said… only to much blocks on one screen… i try to post the compile error soon…


#4

Ok, maybe the error give us some clue about what’s happening. Anyway, you can try to disable one block, compile, disable another block… compile… test and error to see where the error is


#5

I will give a try… :slight_smile:
So many blocks in one screen can’t produce compile errors?


#6

I have a couple of apps with a lot of blocks with no error, and probably there will be people with a lot of more big apps and I haven’t read about it.
How many blocks are you talking about?


#7

I guess about 60 blocks… but spme of them are large… the apk has without any files in the asset folder 3.7 mb


#8

see also tip 3 here

see also
http://twodogapps.com/?page_id=686#Redundancy and
http://twodogapps.com/?page_id=686#Procedures

Taifun


App Crashes when trying to go to next page
#9

thx for the info… but i already know these things…


#10

That is not entirely true. Having lots of blocks cause problems too, but it has to be A LOT (which happened to me).


#11

How about you post a screenshot of the problematic blocks?


#12

if i know which are the problematic blocks i can post them… i will test it tomorrow like josejad said… disable the blocks one by one… i hope thats the way to find the bad blocks…

how many is a lot?? does it matter how large each block is or is it only the amount of blocks?


#13

what about posting an example of one of these large blocks so we know, what we are talking about?
of course we also can continue to guess… as you prefer…

Taifun


#14

I used an older version which worked without compile error… After removing the asset files i got following errors…

Build of WWM_neu requested at Aug 26, 2017, 1:25:32 PM.
Waiting for 165 seconds.
________Creating fragment xml
________Generating manifest file
________Attaching native libraries
________Attaching component assets
________Compiling source files
(compiling com/appybuilder/ortnerapps/WWM_neu/Screen1.yail to com.appybuilder.ortnerapps.WWM_neu.Screen1)
(compiling /tmp/runtime7922014480680148359.scm to com.google.youngandroid.runtime)
Kawa compile time: 7.966 seconds
________Invoking DX
YAIL compiler - DX execution failed.

Error: Your build failed due to an error in the Activities stage, not because of an error in your program. Error: Your build failed due to an error in the DX stage, not because of an error in your program.

[INFO] Locking Screens
[INFO] Unlocking Screens
[INFO] Setting currentScreen to Screen1
[INFO] ProjectEditor: got selectFileEditor for src/com/appybuilder/ortnerapps/WWM_neu/Screen1.scm selectedFileEditor is src/com/appybuilder/ortnerapps/WWM_neu/Screen1.bky
[INFO] YaBlocksEditor: got onHide() for src/com/appybuilder/ortnerapps/WWM_neu/Screen1.bky
[INFO] Setting current file editor to null
[INFO] YaFormEditor: got onShow() for src/com/appybuilder/ortnerapps/WWM_neu/Screen1.scm
[INFO] Ode: Setting current file editor to src/com/appybuilder/ortnerapps/WWM_neu/Screen1.scm
[ERROR] System error: Bad value for vertical alignment – MockHVLayoutBase
[ERROR] System error: Bad value for vertical alignment – MockHVLayoutBase
[ERROR] System error: Bad value for vertical alignment – MockHVLayoutBase
[ERROR] System error: Bad value for vertical alignment – MockHVLayoutBase
[ERROR] System error: Bad value for vertical alignment – MockHVLayoutBase
[ERROR] System error: Bad value for vertical alignment – MockHVLayoutBase
[ERROR] System error: Bad value for vertical alignment – MockHVLayoutBase
[ERROR] System error: Bad value for vertical alignment – MockHVLayoutBase
[ERROR] System error: Bad value for vertical alignment – MockHVLayoutBase
[ERROR] System error: Bad value for vertical alignment – MockHVLayoutBase
[ERROR] System error: Bad value for vertical alignment – MockHVLayoutBase
[ERROR] System error: Bad value for vertical alignment – MockHVLayoutBase
[ERROR] System error: Bad value for vertical alignment – MockHVLayoutBase
[ERROR] System error: Bad value for vertical alignment – MockHVLayoutBase
[ERROR] System error: Bad value for vertical alignment – MockHVLayoutBase
[ERROR] System error: Bad value for vertical alignment – MockHVLayoutBase
[INFO] Adding blocks editor as a listener for Screen1
[INFO] Setting currentScreen to Screen1
[INFO] ProjectEditor: got selectFileEditor for src/com/appybuilder/ortnerapps/WWM_neu/Screen1.bky selectedFileEditor is src/com/appybuilder/ortnerapps/WWM_neu/Screen1.scm
[INFO] YaFormEditor: got onHide() for src/com/appybuilder/ortnerapps/WWM_neu/Screen1.scm
[INFO] Setting current file editor to null
[INFO] YaBlocksEditor: got onShow() for src/com/appybuilder/ortnerapps/WWM_neu/Screen1.bky
[INFO] Ode: Setting current file editor to src/com/appybuilder/ortnerapps/WWM_neu/Screen1.bky
[WARNING] getBuiltinDrawerNames: drawerName = Control
[WARNING] getBuiltinDrawerNames: drawerName = Logic
[WARNING] getBuiltinDrawerNames: drawerName = Math
[WARNING] getBuiltinDrawerNames: drawerName = Text
[WARNING] getBuiltinDrawerNames: drawerName = Lists
[WARNING] getBuiltinDrawerNames: drawerName = Colors
[WARNING] getBuiltinDrawerNames: drawerName = Variables
[WARNING] getBuiltinDrawerNames: drawerName = Procedures


#15

if i make an open source project i will do it… i just want to understand what general produces build errors…


#16

Concerning DX execution failed generally there is SteveJG’s monster list https://groups.google.com/d/msg/mitappinventortest/fLiMEfPh09Q/1Ia0AaQEXogJ

also this

does not look very good…

Taifun


#17

I only use one screen
My app on Samsung S3 gives error
In Huawei P9 Lite works well
I have looked in Debug Panel and these messages come out

image

And

image

How can this be solved? To what is it due?

Thank you!


#18

I use Catlog but i understand nothing :sweat_smile:

2018-04-01-04-10-32.txt (2.9 KB)