Post your Nspire routines here!

[DJ Omnimaga]

no problem, there are over 6 hours between the posts anyway

[t0xic_kitt3n]

It's working now. At first, I thought the bounds would be (1,240) and (1,320), similar to TI-BASIC, but they really start at 0.

[bwang]

Doesn't BASIC's pixel-On follow those conventions too?

[t0xic_kitt3n]

What is the usage of char* scrbuf in the graphics functions?

[bwang]

It's a double-buffer, allocated with malloc() in the calling program. It allows for flicker-free animation.

[t0xic_kitt3n]

How do you write code using the buffer?

[bwang]

Like so:

Code: Select All | Copy To Clipboard

1 2 3 4

char* scrbuf = (char*) malloc(SCREEN_BYTES_SIZE); line(scrbuf, x1, x2, y1, y2); refresh(scrbuf);

[t0xic_kitt3n]

BUt what value do I use for scrbuf? Also, is there a way to draw a line directly to the screen?

[calc84maniac]

BUt what value do I use for scrbuf? Also, is there a way to draw a line directly to the screen?

scrbuf isn't a value, it's a pointer. It is defined by the malloc statement. And to draw directly to the screen, you would use (char*)0xA4000100 instead of scrbuf as an argument to the line routine. This buffer might actually be defined somewhere already, but I'm not familiar with the Nspire include files.

[bwang]

There's really no reason to draw directly to the screen. Drawing to a buffer is faster and more versatile.

[DJ Omnimaga]

What Bwang said. Plus you won't get flickering when stuff moves around (and needs to be erased to do so). I don't know how Nspire ASM/C compares to 83+ Axe, but on 83+ Axe, inverting the entire screen bit by bit takes about 20-30 seconds for 6144 pixels if you draw directly to the LCD. When storing to the buffer then only updating the screen once everything is done, it took about half a second.

[calc84maniac]

What Bwang said. Plus you won't get flickering when stuff moves around (and needs to be erased to do so). I don't know how Nspire ASM/C compares to 83+ Axe, but on 83+ Axe, inverting the entire screen bit by bit takes about 20-30 seconds for 6144 pixels if you draw directly to the LCD. When storing to the buffer then only updating the screen once everything is done, it took about half a second.

Well, on Nspire there won't be any speed difference when drawing to the LCD because it is memory-mapped like the TI-85 model and up. There might be some flickering though, if the screen updates while you are drawing your graphics.

[DJ Omnimaga]

Really? I thought that despite the screen being memory-mapped, there could still be a slight difference? I guess it makes sense that there isn't a speed change if it's really tied directly to the buffer, though.

[bwang]

"Some flickering" is an understatement. Without double-buffering, animations flicker so much that they are nearly unusable.

[calc84maniac]

Well, my emulators actually draw directly to the screen buffer.