On Mon, Jun 30, 2003 at 07:55:25AM +0200, Rainer Hantsch wrote:
> Hi!
>
> In your situation, I would insert a "virtual screen" between your application
> and execution of ncurses calls. All write opertions should also be stored into
> an array hereby, and when reading, use this array instead of a
On Mon, 30 Jun 2003, Marco van de Voort wrote:
> > In your situation, I would insert a "virtual screen" between your application
> > and execution of ncurses calls. All write opertions should also be stored into
> > an array hereby, and when reading, use this array instead of a real read from
>
> In your situation, I would insert a "virtual screen" between your application
> and execution of ncurses calls. All write opertions should also be stored into
> an array hereby, and when reading, use this array instead of a real read from
> ncurses.
> This will be the only way to get around the r
Hi!
In your situation, I would insert a "virtual screen" between your application
and execution of ncurses calls. All write opertions should also be stored into
an array hereby, and when reading, use this array instead of a real read from
ncurses.
This will be the only way to get around the re-map
Hello. I'm currently in the process of porting an old DOS game to
linux using fpc and the ocrt module. The game makes extensive use of
high ascii characters.
Sometimes, if I do : nwriteAC(nscreen, x, y, color, char1); char2 :=
byte((nReadScr(x,y,1))[1]);
char2 will be different from char1, beca
