some questions about RTG library.

[Karlos]

Piru wrote:
Whatever you do, avoid rtgmaster at any cost.

It's one of the worst things that happened to Amiga.

I dunno, I once spilled a full bowl of rice crispies (a cereal I liked before this trauma) and milk upside down onto my A1200D.

That was like the worst thing that happened to my amiga anyway :lol:

[Karlos]

I've never felt inclined to develop any code for it.

As for PPC (OS3.x I mean) stuff, you generally need to do context switches for display handling anyway, so I usually write a few 68K functions that in one go refresh the display, swap bitmaps, lock them etc before returning to the PPC, which just has to worry about calling my 68K function each frame and can run along unhindered the rest of the time.

[Karlos]

It's a good plan.

I had my own display context that upon calling the refresh() function for it, it would switch to 68K, bitmaps unlocked, switched, all IDCMP messages since the last frame gathered into a local buffer, display refreshed, new bitmap locked and then back to PPC.

The PPC would then call native callbacks for the buffered input events.

End result, 1 full context switch but you get all the OS work done and you get to handle your input natively on the PPC in time for the next frame. Not a bad result.

-edit-

Good heavens, did we just agree on a coding issue? :-D