As Wikipedia says "Crobots is a programming game released for the first time by Tom Poindexter in December, 1985 as Shareware.[1] The robots are controlled by a program written in a stripped-down version of C. The robot's mission is to seek out and destroy other robots, each running different p...

The final bit of this saga is that in the end, I just got rid of Curses. The two main calls were move() and addch(). I just wrote wrappers for each one of these. I removed the other curses calls, esp. the refresh() calls and got things working that way. The oddest thing that was the clear() (like CL...

I've made some more progress in the program that I am porting. I got beyond a C68 compile issue just by adding some code back in. Now I'm hitting an issue of the display. Curses does not seem to be clearing the screen when it should. The printw statements are initially working, but then they start g...

I was thinking of doing a ZX81 game, but it would require the sz81 emulator. As far as I know, it is the only one that supports saving zx81 memory to/from disk. But the rules only mention using EightyOne, so scratch that idea.

Tim

IIRC, there might have been some SuperBasic tutorials in a number of magazines, such as QL User, QL World, QL today, etc. The first two are available on the Internet Archive. QL Today is available from "The Distribution", a large download from Urs Konig.

Tim

Looking at the as68 source code, there are a couple of ways to get this message: if ( havebyte == 1 && rval != orval ) if ( rval != R_ABS && rval != R_FIRST ) if ( rval != R_ABS && rval != R_FIRST ) None of those look obvious as to what the problem is. Hopefully someone else ...

As I'm converting all non-curses print calls to curses one, I've hit a snag on the program that I am porting. Everything was compiling fine with Make. I found a few minor issues with main_c. I fixed the last error and now I get this message: as68 main_s main_o jas: (bytes not separately relocatable)...

Tofro, Thanks for the reply. I've not done any curses programming on Unix/Linux before, so I've not read up on any caveats. I have not tried to compile the program on LInux to see if it is a pure curses issue. The DOS version uses it's own display routines and not curses. If it is a curses issue, I ...

Well the example text did not show as I wanted in my posting, Let me try it this way (using dots instead of spaces).

text
......text
............text

Tim

I'm porting an old program from Unix to the QL. It compiles and runs, but the text output has an issue. The part that uses curses seems to run fine. When printing text, the program uses "fprintf(stderr,"text \n"); ". The output on the screen looks like this: text text text as if ...