DLI

[paladina]

What is problem when I change DLIST for GR15 that I become only two row window, the cursor is away,as there was 4 rows... any correction? Thx for help.

 

1 ? "{125}"

10 REM * DL3 *

20 GRAPHICS 15

70 FOR I=33015 TO 33019:READ D:POKE I,D:NEXT I

90 DATA 240,240,66,96,159

100 POKE 82,0

150 ? "HERE THE TEXT,THAT IS LONG 40 CHARACTERS"

DL3.ZIP

[Rybags]

You've overwritten the first LMS Mode E that Antic needs to establish where the bitmap is.

 

You'd be better off with something like:

10 GR. 15:DL=PEEK(560)+PEEK(561)*256
20 POKE DL,240:POKE DL+1,240:POKE DL+2,66
30 POKE DL+3,PEEK(660):POKE DL+4,PEEK(661):REM TEXT WINDOW
40 POKE DL+5,84:POKE DL+6,PEEK(88):POKE DL+7,PEEK(89):REM BITMAP AREA
50 FOR A=DL+160 TO DL+170:IF PEEK(A)<>66 THEN NEXT A
60 POP:TXT=PEEK(660)+PEEK(661)*256+40:H=INT(TXT/256):L=TXT-H*256
70 POKE A+1,L:POKE A+2,H:REM change bottom text window to 40 bytes later
80 POKE A+3,2:POKE A+4,2:POKE A+5,65
90 POKE A+6,PEEK(560):POKE A+7,PEEK(561):REM bottom text window only 3 lines

 

The bitmap area in that example won't be 160 pixels high, it'll be a bit shorter.

You could keep it 160 high by starting the Display List a couple of bytes earlier in RAM.

[paladina]

Not bad...but I need only TWO rows down...not One up and three down... you see my DL, where I change it to TWO ROWS...but the cursor and text is problem...it do as it was 4 rows there... but thenks for your example

[FLY]

Not bad...but I need only TWO rows down...not One up and three down... you see my DL, where I change it to TWO ROWS...but the cursor and text is problem...it do as it was 4 rows there... but thenks for your example

 

 

No použij klasicky GR.15+32 a máš to.....

[Rybags]

80 POKE A+3,2:POKE A+4,65

90 POKE A+5,PEEK(560):POKE A+6,PEEK(561):REM bottom text window only 3 lines

 

That gives 1 row top, 2 rows bottom of text.

 

The OS still thinks you have a 4-line text window so you'll lose the cursor at times. Nothing you can do there - the OS can only handle 4 or 24 lines of text.

 

A more livable solution for the text window might be to start it 40 bytes further on so that the first line is invisible instead of the last line.

[FLY]

80 POKE A+3,2:POKE A+4,65

90 POKE A+5,PEEK(560):POKE A+6,PEEK(561):REM bottom text window only 3 lines

 

That gives 1 row top, 2 rows bottom of text.

 

The OS still thinks you have a 4-line text window so you'll lose the cursor at times. Nothing you can do there - the OS can only handle 4 or 24 lines of text.

 

A more livable solution for the text window might be to start it 40 bytes further on so that the first line is invisible instead of the last line.

 

 

 

No a celkově získáš dole to samý jak u příkazu GR.15+32 s tím rozdílem, že uvidíš všechny minimální 4 řádky.....

[paladina]

Ok and how it correct that I see the last row, now I can put cursor down, whete I dont see him... I need that I see last two text rows...thx.

[paladina]

Rybags! I found it alone :D Its POKE 703... ok...for may two line row I give only POKE 703,2

[Rybags]

That won't work... the OS is hard-coded to recognise only 4 or 24 lines for it's Editor device.

 

Just use 4 lines for your text - you'll probably end up needing them anyway.

[mono]

@Paladina: look at my reply on atarionline.pl: http://atarionline.pl/forum/comments.php?DiscussionID=472