How do you close Screen2 and display Screen1 in the background with the same page visible before switching?

Wow, the dynamic table is perfect :slight_smile: ...I just did some quick appearance setup, but now I will start updating my app from simplifying the button blocks, following your suggestion, to lighten up my app. I don't see any of your changes in the buttons on screen 1, so I can continue working on my file, right?

Then I'll move the table to screen 1 and copy your blocks one by one. During this work I will try to better understand all the poetry that the blocks contain :slight_smile:
Finally I will try to understand the table export method.

I don't see big corrections in the home. I just noticed that the height of the first label is set to "fill container". Can you tell me what other additions did you make? ... so I apply it in my file.
Thanks a lot!

I've simplified the button blocks and this works great! :slight_smile:
I transported the table to screen1 and I did my best, but I wasn't able to fit the blocks well. Could you please take a look? ...I wanted also the data to be loaded when I click the List button, without having to click on Load Data. At this point HA1 can be set on "not visible".
Then it's necessary to check the whole combination of blocks "Hide Pages".
I send you my file. Thank You
:innocent:
Nadi3_updatedbyEla.aia (388.7 KB)

Your project is getting worse, racing my computer CPUs to over 100% with a single block move, making editing unmanageable.

I will try with different browser....

1 Like

Yes, it was fine before moving the table. I believe there is conflict with TinyDB blocks

Not really any better with Firefox. The table, being dynamic, should not be having an impact, as the blocks will only be run when the table is loaded. I was having lag issues before you moved the table.

My guess is that the app is having to load so much stuff, all in one go, and that there is a loop of some kind causing the problem.

You may need to take all that you have learned and start again.:frowning:

...like a mandala? ... blown away with a single wave of the hand? :innocent:

..but after reducing the button blocks, the app responded very well
... were you able to eliminate the unnecessary blocks?

if you can do a bit of cleaning of the blocks, I do a check of each element before starting all over again

maybe we can eliminate the whole sequence of the "hide pages"? ... do you think it is no longer necessary if we have everything on the same screen?

If i get some time, I will have a good "chop" at your last version (though it will be slow work) to see if I can repair it

maybe you can just take a picture of the blocks and point me to some important elimination, then I'll do it ... especially let me know which of the TinyDB blocks I can delete, please :slight_smile:

Found the problem it is the Salva button block, even just opening the backpack with that block in it causes CPU overload and page freeze.

This will need re-working, it is highly repetitive in any case

I cleared some blocks, now it is lighter ...please try to see if you can do something with this version :slight_smile:
Nadi3_updatedbyEla_Lighter.aia (387.2 KB)

"Found the problem it is the Salva button block"
aaah, great!

You may want to consider using listviews/listpickers instead of big displays of buttons for selection, and to use lists to store the selected data, then you are not having to iterate over button states all held in memory to then save. It may not be as pretty, but will be more efficient.

Here a simple example using a spinner
spinnerSelect.aia (2.9 KB)

Yes, ... but I want it nice and clear to see :grinning_face_with_smiling_eyes:
... for a person who feels his own pulse, collecting data must be very simple and intuitive, so big buttons :joy:
... I think for now I will stay with this version and I will be very grateful if you help me to simplify it as much as possible

yes, I have seen the spinner, ... using listView or other similar packages, is very binding. I have to be free to handle every button. As you have seen, sometimes when I press one button another has to be deactivated, etc.
Then in level 1 of the pulse reading things are very simple, but then in the advanced levels the information will be more complex.

which is why you should use lists, and avoid repetition of button displays :slight_smile:

..by "more complex" I mean that I will probably have to use some drawings, and maybe the buttons will not be a simple list but located in various places on the page ... but I don't think about it yet. For now I would like to conclude this first level, and let the pulse reading practitioners use the app, to test it, ... then I will decide how to proceed.
...do you think you can do something with that file I sent you?