Boo-yah! But what do you mean by no goto?

Penguin, really, we don't care if you create a 2-page-app from it.

Boo-yah! But what do you mean by no goto?

The reason you corrupted your memory was because when it said Error:Memory, you pressed the Goto option which took you to a place it shouldn't have. I just made that menu only show quit now.

Penguin, really, we don't care if you create a 2-page-app from it.

I realize that. You guys don't care. However, a lot of people who don't have the same connection with this app will. A one page app that does all this stuff is amazing. Once you go to two pages, you have to ask the question why is this thing really two pages? and why couldn't the author have made it all fit into one page?

Also, two pages makes things run slower internally. Switching from one page to another isn't exactly easy and it makes the whole organization of code different.

0.o awesome update, methinks I'm going to be using some of these things a lot (already used the insta-APD multiple times in the process of writing a program)

zstart seems to collide with DCS7...

Nvm that, had an old version installed by mistake.
Whee, new features! So cool!

A bug report: In the basic editor it didn't work to press FORMAT (2ND before of cource) and then go to Axes off, when I hit then enter the tolken appeared and behind that were a lot of question marks and there were no more lines after that code. When i exeted via  2ND MODE and then go back in the program is back to normal, just the AxesOff isn't there. I had to acces it via the catalog.
EDIT: I tis aswell with all the other tolkens in that menu

I see the problem there. That menu is a different context, just like the mode menu. The reason it glitches though is because I didn't know that . Also, the problem is really only prevalent in MathPrint, so I didn't notice it.

zstart seems to collide with DCS7...

HA! I know. Here are the problems, with solutions:

• DCS will create OFFSCRPT whether it is using it or not. This means if you have a startup picture or a startup program, DCS will get rid of it even if you  tell it not to create it. (I think the solution is apparent here)
  
• DCS chains to the rawkey hook, which I am very impressed by. However, the second time you run DCS, it chains to itself. A simple page check on the rawKey hook would clear this up.
• Lastly there is the parser hook. For this one, I don't blame kerm at all for killing my hook. Parser hooks are a pain to chain to. The workaround for this is to either disable DCS's parser hook, or just press ON+CLEAR when you quit DCS. But honestly, kerm and I do almost the exact same thing with the parser hook, so this probably is not a problem. Actually, he does chain, it's just the same deal as the rawkey hook.
  
  You know what, I'm going to go post another bug report. Although, of course I'll be much nicer ;) However, if he ignores it again...
  
  Edit:
  
  Quote from: aeTIos on November 09, 2011, 03:18:17 pm

  Quote from: Hayleia on November 09, 2011, 12:05:50 pm

  Feature request:
  Draw the functions in Full speed mode *.*
  That would be very nice :D
  

  Uh, it already does that in 15mhz (OS is slow)
  

  
  That is correct. Basic programs are run in 15MHz mode
  
  Edit2:
      Yay, he did listen. OFFSCRPT now works seamlessly with DCS. Once he fixes the chaining issues, they will be compatible.