Awesome! I'll have to re-practice my TI-BASIC to remind myself of how to use getkey and stuff to try this.

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.

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

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

DJ, I forgot that Asm( can only run programs, not hex code.  However, I found that I can use the regraph hook to turn on the parser hook when it's been turned off.  Since I can prevent the graph screen from being drawn at all, I'll use a command -- so far, ZoomSto -- to turn on the parser hook.  That way, Ti-Basic Text-Based games will STILL run faster with Correlation than without it.  (If this doesn't make sense, just trust me

I'll be doing the rest of my in-house testing/coding next January.  I have been working on the Correlation Manual, and I plan to have it released before the end of the month.  Those of you hoping to test Correlation might want to read through the manual when it's released

Aah ok. Just one thing, though, especially since it's an utility to help programmers: try to not make the readme excessively long. A lot of people are turned away by Celtic III readme because it's too long and they use xLIB readme instead. Some people prefer larger readmes, though, so it's a good idea to maybe include two versions. Some people just get lost when they see a wall of text. X.x

Rather than a read-me, it's like a "For dummies" book, in pdf.  However, if people find it too long during the testing period, I will take your advice and include a quick readme.  Like Axe, though, the concept requires a lot of "how to do" rules, and thuse more documentation is required