Normally, if nothing has changed since the last time you graphed equations, displaying the graph screen will simply cause your graph to load instantly, there is no redrawing.

In Ti-Basic, something like "1->Y₁" will cause DispGraph to redraw the entire graph.  But it's not the most optimized way.  Is there anything faster?  A cookie and a bag of peanuts goes to the helpful person who gives me the fastest, most optimized command to force a graph redraw upon reaching the command DispGraph.

Thanks, everyone!

Quote from: Hot_Dog on December 16, 2010, 12:32:36 pm

Quote from: graphmastur on December 16, 2010, 12:31:34 pm

Quote from: Hot_Dog on December 16, 2010, 12:29:07 pm

Quote from: graphmastur on December 16, 2010, 12:27:43 pm

Sure, just b_call 4FF6 out of an assembly program. Or, if you want, check bit 0, (iy+36h), and store if it's set or not. If it is set, reset it, and set it when you are done at the end.

Oh, sorry, I don't want to disable the hook.  I want to use the Trace hook to disable tracing

Oh, if you want to disable tracing. I see. Try just setting the zero flag. It should prevent the trace by preventing it moving, blinking and being visible.  I'll try this now, and see what I get.

Let me know if you don't even get the graph screen after setting the zero flag.  That's my goal

Are you saying you just don't want the graphscreen to show up, or the graphs on the graphscreen?

Oh, I want to use the trace hook to "fool the calculator" into thinking that the user never pressed Trace in the first place.  No graph screen, no graph, no cursor, no nothing.

Quote from: Hot_Dog on December 16, 2010, 12:29:07 pm

Quote from: graphmastur on December 16, 2010, 12:27:43 pm

Sure, just b_call 4FF6 out of an assembly program. Or, if you want, check bit 0, (iy+36h), and store if it's set or not. If it is set, reset it, and set it when you are done at the end.

Oh, sorry, I don't want to disable the hook.  I want to use the Trace hook to disable tracing

Oh, if you want to disable tracing. I see. Try just setting the zero flag. It should prevent the trace by preventing it moving, blinking and being visible.  I'll try this now, and see what I get.

Let me know if you don't even get the graph screen after setting the zero flag.  That's my goal

If the trace hook is on, is there any code that will keep tracing from happening whenever Trace is using inside of a Ti-Basic program?  I have a very important use for Trace that cannot make use of the parser hook

By the way, it's hook $9BA8

The only thing, though: Using Asm() is a bit slow by itself, so maybe sometimes you will be best not disabling hooks altogether even when Correlation isn't needed. It will depend how many sub-programs do you have and how much RAM left.

I'm thinking something along the lines of Asm(FDCB368E).  I'll have to check this out, I didn't think that it could be slow like this.  I thought, though maybe I'm wrong, that using this would be a good idea if there were at least 6 lines of code that didn't need Correlation

Quote from: Hot_Dog on December 15, 2010, 09:08:43 pm

GOOD NEWS, EVERYBODY!

I had someone ask me at one point if Correlation would slow down Ti-Basic programs, to which I had to reply that all parser hooks slow down Ti-Basic programs, even if slightly.

But I forgot that one can use Asm( to run hex code.  So I'll place guidance in the Correlation Manual to turn the parser hook off when not needed, and turn it on again when needed.  When used properly, TI-BASIC TEXT-BASED GAMES WILL ALWAYS, ALWAYS RUN FASTER WITH CORRELATION THAN WITHOUT IT.

Fixed.

Ha ha ha

Okay, problem solved.  Something called "temporary variables," which I never heard of until now.

YAAC = Yet Another Asteroid Clone.  Probably the best version of "Asteroids" I ever played