thank you. you have at least halved the time i projected it to take for me to ready my project for release and spared me massive quantities of coding. How would you like to be credited?

Nice Thepenguin77. Btw, did you plan the addition of ungrouping and support for group names with fewer than 8 chars, allowing the user to not have to fill empty spots with space tokens?

Quote from: ACagliano on July 06, 2010, 09:39:23 pm

thank you. you have at least halved the time i projected it to take for me to ready my project for release and spared me massive quantities of coding. How would you like to be credited?

My guess is by rickroll.

wut? o.O

what sort of problems did the first one have? because i tried to use it and it crashed. i had a full memory dump (RAM and Archive) and now my calc randomly crashes when i try to do some basic functions or run certain apps.

I'm hoping ARCHUTIL will be of some service in recovering my archive.

That's not a bad idea. I don't think ungrouping would be hard, I would do the whole thing at once though.

Also, I guess by the way it works, you technically only need one space for the group name. So it would be "A_" or "AB_" or whatever. You just have to stick a 0 in there so the OS knows the name is done.

I guess I could technically do the same for the second list as well, my program would just see the + or - as the start of the next variable and then . That would work.

What I mean is I have a little routine that replaces all the spaces with 0s. So putting a space after it technically makes it look like "GROUP2", 0 after I parse it.

I suppose I could technically not require the space. The only problem is, the less you do in basic, the bigger the program is. And since the program gets its sized doubled by unsquishing, it's a tough balance.

What I mean is I have a little routine that replaces all the spaces with 0s. So putting a space after it technically makes it look like "GROUP2", 0 after I parse it.

The way it currently works, you only have to put one space after the group name.

I suppose I could technically not require the space. The only problem is, the less you do in basic, the bigger the program is. And since the program gets its sized doubled by unsquishing, it's a tough balance.

Since memory is the goal in basic, adding more features might not make it smaller. It requires less on the user's part, but the asm program gets bigger.

lol I just quoted myself

what sort of problems did the first one have? because i tried to use it and it crashed. i had a full memory dump (RAM and Archive) and now my calc randomly crashes when i try to do some basic functions or run certain apps.

I'm hoping ARCHUTIL will be of some service in recovering my archive.

Did anyone see this bug report?


The calc now requires ON+CLEAR to turn on.
Any of the reset memory functions freeze.
CalcSys Crashes

Edit: ArchUtil was able to recover my archives once i put it back on my calc. Now, seeing my above problems, should i do an OS reinstall.

Yeah, if a full reset can't fix it, you don't know the problem, and you don't want to leave your calc as-is for diagnostic purposes later on, I agree with DJ.