Hey, I'm going to learn ASM (I know a bit), and I've some questions:

1. bit editOpen, (iy+editFlags) doesn't seem to work for me on the 84+
2. How can I return to the ASM program after _ExecuteNewPrgm? (It returns to the homescreen)
3. Can you load the carry flag directly in another bit?
4. Can you run a BASIC program from ASM without deleting and recreating it?

More questions are following

Thanks in advance!

Hm, how are you using it?


Not quite sure what you mean here, could you please elaborate?

Is this what you need?:

Code:



Sure, this code installs an error handler that you can use to do whatever you like if the BASIC program hits an error:

Code:

Wow, many thanks so far! For running a BASIC program, I don't need error checking because it runs only 1 program and I'm sure I will test it, so that no error occur.

It works so:
I've created an ASM program, that installs a key hook.
If someone anywhere press [LINK], it executes some code. I hope you understand this
That code is first checking if my prgmR exist, and if so, it runs the program.
But if you pressed [LINK] in the program editor, my aim is to return to the editor after running that program, because now it just returns to the homescreen.
Hope this helps!

5. How can I insert text at the cursor in ASM? Let's say you read Ans as a string, and that would be inserted at either the homescreen or in the program editor.
EDIT: it seems to do something with Recall Queue

6.
Code:

works fine without a hook, but if I nested it in a key hook, it gives me a Memory Error. Why?

It seems to me that you need to check the context when your hook starts, and if it's the editor, it needs to close the editor context, run the program, then re-launch the editor context. See also below.

If the editor context is open, it inserts the entirety of your free RAM into the program it's editing. When you close the editor, it returns any unused RAM back to the free RAM pool. If you're calling _ParseInp from a keyhook, you need to make sure that the editor context is not active, and if it is, you probably need to close it first.

Edit: To close the editor context, you either want to go through the _NewContext rigmarole with a new context of cxQuit/kQuit (that is, the Homescreen), or just call _Putaway on the editor context, then _NewContext afterwards. I don't like the latter solution, because being in no context at all sounds dangerous.

Code:
still doesn't work within the key hook. Any ideas?

Kerm, I feel as if you are one of the few who understands the edit buffers well. I have never seen, and could not find one when looking for one, an example of them being used. Could you point PT_ (and me) to an example of them being used?

It's not definitely the edit buffer, my program didn't work from the homescreen as well. I'm only asking a small (?) code snippet for running a BASIC program with ASM in a key hook from the homescreen. Additionally, it would be fine if it could be done from the program editor.

*bump*
I've still no idea how to do such stuff, and where I can find it. I've tried the code on WikiTI - don't help. Even Googled it - nothing found. Please please please could someone write a code snippet for me (and other?) that does the following:
- Check if you'r in the program editor/edit buffer (bit editOpen doesn't seems to work)
- Run a BASIC program which name is in OP1 (the standard) - no Memory Error please
- After that program run, returns to the ASM program which calls the BASIC program
- Return to the program editor/edit buffer

See also my other posts in this topic.

If you don't understand it, please ask me

See my post above!

Another question: how can I disassemble a part of the OS. I.e. what should I do when I want to know how _ParseInp works? I had the idea to do

Code:

but then I got a bunch of BASIC-commands, which is hard to translate to hex.
My second try was to load the contents of _PutS into the graphscreen, and make a BASIC program to get it, but I don't get normal ASM I guess

Code:

You're going about it the wrong way, the easiest way would be either to disassemble the OS or use the debugger of an emulator to step through the instructions until you actually get to the bcall code. The EF opcode (bcall) will jump to the address $0028, do some magic to save the current flash page we're on, find the address of the bcall (the two bytes after the EF opcode), which flash page to load based on the bcall, jump to the code (look for a bunch of pops followed by a ret), restore the flash page, and quit. Calling _PutS treats the assembly instructions as (TI) ASCII characters and will continue drawing until it comes across a 0.

So in fact the two bytes after EF tells the OS which flash page to load? Each time you call _PutS, is it always the same flash page?

I second chickendude's opinion: stepping through the bcall in an emulator is the easiest way to see how it works. Single-step through the bcall setup code he described; you'll know when it's ending because the OS pops most of the registers and returns. You'll then be in the meat of the call's code; make a note of the page and address of the start of the call, and if you want to see it again, you can avoid the bcall setup code by just setting a breakpoint at that address.

I'm diving into ez80 programming, but that seems to be hard
I know how to turn the screen black in ASM, but I can't access single pixels
Can anyone help me?
I've this so far:

Code:

Looks like you need to set up your palette. This page:
http://wikiti.brandonw.net/index.php?title=84PCE:Ports:4000
Will provide some more information. Simply search for CopyHL1555Palette. Hope this helps!

SPASM-ng's order of operations REALLY, REALLY sucks:

Code:

It turns this into ((VRAM+320)*50)+50. That's VRAM*50 + 320*50 + 50.

Edit: To quote SPASM-ng's manual: ^ This is the laziest nonsense ever and makes me sad. Besides being terribly unintuitive for anyone who (1) has learned math, or (2) programmed in any other language, it teaches programmers terrible habits if they haven't programmed in other languages before. I intend to fix this in SPASM-ng at some point.

I saw that SC supports ez80, but how would the header look like?
And how is the ti84pce include file called?

When looking at the Parser Hook at WikiTi, what value should I load in HL, if it should be an Asm( token, instead of sin( (for example), and how would I know that?
Btw, this is in ez80, if that makes difference.

I'm trying to get the countdown in ez80 working (see this), but it didn't start to count down
Here is my code:

Code:

When I tested this in CEmu, the debugger told me it won't count down, although it has the right value in it
Any suggestions to make this working? Thanks!

I dunno much about ez80 asm, but from the doc you linked I'd say you also need to set bit 0 of (F1000C).

I somehow removed a part of my code :O
This is my full code:

Code:

^ that doesn't help anything