A third way to pset

[barok]

yeah. i was surfing the net, when i found a third way to pset a pixel. it's slightly faster than poke offset&, colour, but not much, because it constantly accesses the def seg.

def seg = segment + y * 20

poke x, colour

if it turned out everyone knew this already, then shoot me. if not, then :king:

[Mech1031]

I didn't know there was a 2nd way! anyway, congragulations on your discover.

[RST]

Newb qustion, but... I knew there was a second way involving peek/poke but never learned it. Can someone show how or link a FAQ? Thanks.

[na_th_an]

http://faq.qbasicnews.com/?blast=Plottin...enThirteen

[Zack]

Nice, Barok. Never knew that...*turns it into a subroutine*. Ah, now it's saved in my little library of usefull functions.

[Plasma]

Actually, if you program is compiled you can just set the segment to A000h once and then use short ints (in effect they are unsigned):

poke y * 320 + x, color

If you're running in the IDE, and still want the speed of short ints, you only need to set the segment once for each half of the screen. A000h for the top half, A7D0h for the bottom.

[relsoft]

yeah. i was surfing the net, when i found a third way to pset a pixel. it's slightly faster than poke offset&, colour, but not much, because it constantly accesses the def seg.

def seg = segment + y * 20

poke x, colour

if it turned out everyone knew this already, then shoot me. if not, then :king:

Optimus and Mr. Chow used that in their demos. ;*)

Never got the hang off it though, I use a scanline poke. ;*)

[Antoni Gual]

I have used it for years, you can find it at every source in my page. I learnt it from Optimus. I use it to build a table of scanline segments and then search the table for each line. It can't be used if you are filtering and PEEKing from line-1.
In general I find it more IDE friendly than POKE lineoffset%+x%, this one is slightly faster but can't be used from the IDE.