That's pretty interesting.  Personally, I think you should make a new topic, in case some people don't see it here.

I like the new splash screen.

Some fresh news...

After infinite failed attempts, i finally found a way to force the os to open up the prgm editor upon exiting the app.
However, since the method is quite tricky, i won't get the render i wanted.

The sequence will look like this :

- An error is encountered during the process.
- The error details are displayed.
- The curious user selects the goto option.
- The app automatically quits.
- The os immediately shows a syntax error.
- If goto is selected, the prgm editor is opened for the concerned prgm (source or include), the cursor pointing to the line where the error was encountered.

Unfortunately, here are the drawbacks :

- The ugly ERR:SYNTAX menu.
- The user will have to select the goto option twice (one time in the app and one time when back to the os).
- Not possible to point to a token, only a line (The user will have to use his brain a bit, despite i didn't wanted that).
- I will have to modify my code again =[

I wouldn't say i'm proud of it but it's better than nothing and at least, it works =]

PM sended.
Thx for the tip zippy =]

Nice!

Very nice! I don't code ASM, I'm more into the Axe side of things, but this sounds pretty neat.

Looks awesome!!!

I use mimas now, but am frustrated over the lack of macro support. This will help a lot. Maybe you could include support for including appvars as headers? like convert ti83plus.inc into appvTI83PLUS. That way, we dont have to define every b_call address or system ram pointer/flags offset.

Looks awesome!!!

I use mimas now, but am frustrated over the lack of macro support. This will help a lot. Maybe you could include support for including appvars as headers? like convert ti83plus.inc into appvTI83PLUS. That way, we dont have to define every b_call address or system ram pointer/flags offset.

Thx =]

asmdream only reads prgms, which can be sources, label libraries and macro libraries.
With prgms, the user is free to consult them, just like he'd do on a computer.
I plan on creating maybe half a dozen includes with useful equates.
More precisely, this is the next thing on my todo list =]

*****

Oh, hey, did your question ever get answered about jumping to errors? I do this in Grammer, so I do know how to do this, but to make life easier, you will need to only allow it for programs in RAM. Anyways, what I would do:

-At the beginning of the program, store the source file name at address 9652h. Since you must at some point have the name of the program in OP1, just copy OP1 here.
-Next, get the size of the program and make sure to have a pointer to the data (not the size bytes)
-Store the address of where the program data is at 965Bh
-Add the size of the program to the start address to get the end of the source file and store it to 965Fh

Now you are all set up. When you need to jump to an offending byte, store the address to 965Dh and then just use bcall(_JError)

I hope this helps!

I already tried this method but couldn't get it to work like i want.
You convinced me to try again.

Thx =]

*****

BONUS : asmdream assembling a prgm that creates a basic prgm, and run them both :

Thx =]

*****

Oh, hey, did your question ever get answered about jumping to errors? I do this in Grammer, so I do know how to do this, but to make life easier, you will need to only allow it for programs in RAM. Anyways, what I would do:

-At the beginning of the program, store the source file name at address 9652h. Since you must at some point have the name of the program in OP1, just copy OP1 here.
-Next, get the size of the program and make sure to have a pointer to the data (not the size bytes)
-Store the address of where the program data is at 965Bh
-Add the size of the program to the start address to get the end of the source file and store it to 965Fh

Now you are all set up. When you need to jump to an offending byte, store the address to 965Dh and then just use bcall(_JError)

I hope this helps!

Tried it again.
Here are the encountered problems :
1) _jerror always jumps to the 1st byte of the prgm, no matter which value i stored into nextparsebyte ($965D).
2) My custom error messages are already coded (without error handler) so it would be definitely good if i could find a way to directly jump to the problematic token (avoid the "ERR:XXXXX" menu display).