to many UI elements? opening up more memory

[mtraven]

I'm building a project , using the UI elements, that displays a bunch of numerical digital readouts that change rapidly. The program structure is very much like "GUI example", in fact I gutted it * build my own around the general structure. In the current version, each digit uses a label, thats 10 per readout. Everything works very nicely until I try to add the 6th readout (labels ~50-60)... The whole thing pretty well freezes on me (boots, but does not update). I need to get to 10-12 readouts

Thinking its a memory issue, I started looking at how to get access to more memory. I loaded a noOTA partition scheme that gave me my full memory (3145728 bytes). This dropped by flash usage to 26% (from~65) and my RAM usage remains steady around 13%. But this had no effect on how many labels I could place. Not knowing much about this sort of thing, I then investigated the stacksize argument to App()...that seemed like the sort of thing that might control how much memory the app can use. To my surprise, I found an inverse relationship between stacksize & the number of elements I could use. That makes me think there is some fixed amount of memory that the class gets, but stacksize seems to come out of that.

Do I have that right?

Is there a way to open up more memory (it seems like the chip has it) ?

being able to delete labels could also help me, unclear as to how I would do that. whats the proper way to do that?

If you're thinking its crazy for me to use as many labels as I am, I'm with you. I am working on an alternative approach in drawing primitives, but I'm having issues there to. I'll post a separate issue for that stuff.