[TI ASM] I'm so lazy! Getting _iLine to draw to buffer only

chickendude · Post by **chickendude** » Tue 17 Oct, 2006 7:47 am

set 0,(iy+plotflags+3) ;0=bufferonly
That's what it says in the System Routines SDK, but it doesn't appear to be doing so...

threefingeredguy · Post by **threefingeredguy** » Tue 17 Oct, 2006 8:44 am

set bufferOnly,(iy+plotFlag3) worked for me.

King Harold · Post by **King Harold** » Tue 17 Oct, 2006 1:24 pm

works for me aswell
you're not using fastcopy aswell are you? probebly not but just make sure..

KermMartian · Post by **KermMartian** » Tue 17 Oct, 2006 3:02 pm

It's set 0,(iy+plotflags3), not set 0,(iy+plotflags+3). Notice the absense of the plus sign in the correct one.

King Harold · Post by **King Harold** » Tue 17 Oct, 2006 4:18 pm

oh, just read over that
well yes that + has to leave..

KermMartian · Post by **KermMartian** » Tue 17 Oct, 2006 5:39 pm

That's his problem. And there would be no problem whatsoever with him using a fastcopy routine; it just copies buffer-->lcd.

King Harold · Post by **King Harold** » Tue 17 Oct, 2006 6:14 pm

Ofcourse it would be a problem, he only wants to draw to the buffer do NOT to the screen, so if you accidentally copy it anyway...

KermMartian · Post by **KermMartian** » Tue 17 Oct, 2006 7:43 pm

Nope, you don't understand how it works. Most TI-OS drawing and graphics calls, by default, write to both PlotsScreen _and_ directly output to the LCD, or jus toutput to the LCD. This can be a big headache for ASM programmers, and flags like the flags in (iy+sgrflags) must be set correctly for text. This is the flag that needs to be reset for line and other graphics calls.

chickendude · Post by **chickendude** » Tue 17 Oct, 2006 8:36 pm

Oh my god. Haha kerm you are amazing!

KermMartian · Post by **KermMartian** » Tue 17 Oct, 2006 9:23 pm

chickendude wrote:Oh my god. Haha kerm you are amazing!

In a good way or a bad way?

Timendus · Post by **Timendus** » Tue 17 Oct, 2006 10:40 pm

Dude... his point was that he should make sure he's not copying the buffer to the screen himself before trying to figure out what's wrong with the flags...

KermMartian · Post by **KermMartian** » Tue 17 Oct, 2006 11:30 pm

Timendus wrote:Dude... his point was that he should make sure he's not copying the buffer to the screen himself before trying to figure out what's wrong with the flags...

I realize that, but I would hope he's checked something as trivial as that first. I suppose that's an unfair expectation then.

chickendude · Post by **chickendude** » Wed 18 Oct, 2006 3:17 am

Good way, of course!

King Harold · Post by **King Harold** » Wed 18 Oct, 2006 7:32 am

kerm_martian wrote:Nope, you don't understand how it works. Most TI-OS drawing and graphics calls, by default, write to both PlotsScreen _and_ directly output to the LCD, or jus toutput to the LCD. This can be a big headache for ASM programmers, and flags like the flags in (iy+sgrflags) must be set correctly for text. This is the flag that needs to be reset for line and other graphics calls.

..dude.. if he'd somehow be copying the buffer to the LCD the flags wouldnt make a difference (it would be shown anyway, just a few T-states later) and just suppose he'd set them up right and then still left a fastcopy in?
Which is the first mistake I can think of, I probebly would have made that mistake

atleast once..
So, yes I do actually understand how it works.

KermMartian · Post by **KermMartian** » Wed 18 Oct, 2006 3:16 pm

This was settled three and four posts ago.