Yeah, I figured. Either way, it is good practice to let the app exit if it isn't supposed to do anything. You can still use the bcall which will exit an app automatically, without crashing. Usually if I download an app, I don't expect it to crash if I try to run it

Okay, so I was playing around with that idea yesterday about how the diagonals in Pascal's triangle are simply the sum of the diagonal before it and I combined that with some other things I did with it and I came up with a few things:
First, P_n(r)=(r+n)!/(r!n!). This means that if you want to check the third diagonal for the seventh number, n=2 and r=6 (because they offset at 0). This yields:
P₂(6)=(6+2)!/(6!2!)
P₂(6)=40320/1440
P₂(6)=28

Because of the closure property under addition and multiplication of integers, we also have that P_n(r)=P_r(n) which can be useful, too. We can also look at _nC_r alternatively as:
P_n(r)=_r+nC_r
or
P_n(r)=_r+nC_n

We also have the definition of _nC_r as _r+nC_n=n!/(r!(n-r)!), so we can show the above statements true:

_r+nC_r=(r+n)!/r!((r+n)-r)!
_r+nC_r=(r+n)!/r!n!
and:
_r+nC_n=(r+n)!/n!((r+n)-n)!
_r+nC_n=(r+n)!/n!r!

So yeah, just a little fun I am definitely adding this to my master notebook

How would it work? Can you give an example?

Yeah, I plan to make a new update soon, anyway. I have to fix >, I have added // comments as well as 2 other commands. I am working on command 93 which will let you insert a list somewhere inside another list. I also need to add 3 more commands to do that for strings (deleteing bytes, inserting, and inserting other strings).

Yeah, if you need to, you can use IS>( to jump forward a specific number of lines, but that is a little advanced and complicated.

Hehe, all it does is draw inverted vertical lines, updates the screen and then reinverts so that the screen is back to normal, but it doesn't look like it That is why I don't make commands that automatically update the screen It makes graphics faster and nicer looking

EDIT:
Um, since it uses 2 bytes, I would rather not, Scout. Also, Pause A will cause it to cycle between fast and slow, but I guess that is an effect I forgot to add Pause 5 in mine. So where is the optimisation? (assuming I had added Pause 5)

Hehe, nice As a few tips for optimisation, instead of AxesOff, ClrDraw, and DispGraph, inside the ReCode loop you can just do Fill(0. Also, if you want to, you can do dim(22,"FDCB00AE",40 instead of using two dim( commands Thanks, Scout!