also i fixed the runtime error
(Canned Reply: ABG - Download those blocks and post them here)
You can download and post each of those event block(s)/procedures here ...
P.S. These blocks can be dragged directly into your Blocks Editor workspace.
See Download Block Images for a demo.
...
Can you make a screen recording of your attempt and post it somewhere we can see?
this is what happens
I'm glad you mastered Do It.
It should make things easier debugging the next bug.
yeah, I thought that you did do it on the control blocks. I removed several unnecessary blocks, as well as fixing a few tiny db naming issues.
It still strangely doesn't work.Still brainstorming.
Remind us what your app is supposed to do,
where it is failing, and
(Canned Reply: ABG- Export & Upload .aia)
Export your .aia file and upload it here.
.
Working_Gcc_copy_backup013125_copy_copy.aia (607.3 KB)
GCC is an app that is supposed to keep track of different projects like knitting and one day save those projects.Thank you for all the help.I'm gonna try comparing all of the tiny db tags again to make sure nothing is wrong with those.
nope. still the same.
It's counterproductive to abbreviate too much on your names.
P is for Project?
Then say Project.
Also, if you are going to use the same fixed piece of text in multiple places, like as a TinyDB tag, encapsulate it in a value procedure and use the procedure call result for your TinyDB access .
Sample:
In this sample project, these two procedures are the only ones that know the TinyDB tag for current user. That eliminates lots of opportunities to use the wrong tag, through typo or forgetfulness.
P.S. It's good that you are reading your code, and checking for consistency.
If you have an available sibling or stuffed animal, walk through your code with them, explaining each piece and how it fits into the app. The act of explaining and reading aloud helps uncover problems.
THERE! the red is the problem. or at least i hope it is. i will move the red clear tag to the Back Button so that it will only clear when everything is done. as for the set global red box, that will be deleted and be replaced with a procedure.
I tested on this code and it for some reason the numbers still are just showing up as 0. I think its either it deletes the progress before initialization, or after leaving, or it might be the naming system for the tiny dbs.in that case, i will have to redo the entire naming system, which I will do just in case.
yeah no, its not the naming system, so here is a list of things i will check
that might be interfering.
- initializing deleting before label get initialized
- deleting progress when going back
- check if there is another saving system that overwrites the progress into the wrong format
I might think about making a list saving system, that splits at spaces after the main item has been retrieved.
It's good that you are learning to read code critically.
Every piece of code has behind it a set of unstated assumptions and promises made, which much be verified by the code reader.
