Yeah I mean if both wouldn't fit in one page anymore. Otherwise it's best to keep everything in one page. Btw I posted a news (from your auto-upload-approval topic) finally

Good to hear, good job

Nice Xeda, looking cooler and cooler!

Hm, so I was over on TIBD when I got an idea to make a command to delete or insert list elements. I'm not sure why there isn't an OS command (or is there?) for this since there are bcalls... For the deleting, you need to specify the offset into the list, the number of elements to delete and which list you want to perform the function on. I have not actually added the insert command yet, but deleting works like this...

Let the list to play with be {0,1,2,3,4,5,6,7,8,9}

To delete 4 elements starting at the 2, you can do:
dim(91,2,4,{0,1,2,3,4,5,6,7,8,9The result will be {0,1,6,7,8,9} in Ans
Alternatively, if that list was stored to L1, you can do:
dim(91,2,4,0or
dim(91,2,4,L1As a note, they directly modify the list, so there is no need to do something like this:
dim(91,2,4,0→L1
Blegh, now I wonder if I should make similar commands for strings...?

There are two things that I know of that can cause a crash:
1) Improper syntax (usually problems are caught before they can cause an error)
2) Certain Apps or assembly programs might overwrite the RAM areas used by BatLib

To fix the first one, just make sure you use proper syntaxes. To fix the second one, after running an app or assembly program, you can reinstall BatLib either by running BatLib or using the included prgmZINSTALL. Not all asm programs will cause problems and not all apps will.

Also, I realised as I was posting this that I never updated prgmZINSTALL from the beta version of BatLib, so here is the version that should work on all future versions of BatLib.

Hmm, well I guess I could do that... (sometime later...) Okay, so I removed the commands below, so if you use them, it returns ".SAFE"
12-StoBytes
14-VarEditByte
17-MemEdit
41-GetStats (It might be buggy)
64-CopyProg (This doesn't work for some times... the program version works, though )

There shouldn't be any other commands that edit vars or memory that could be unsafe

EDIT: Also, I forgot to not include commands 91 and 92, so this has command 91 and 92
91 is DelElements: deletes elements from a list
92 is InsElements: inserts elements into a list (with a value of 0)

Both use the syntax dim(91,Offset,#Elements,List#

Offset starts at 0
#Elements should be greater than 0
List# can either be a direct list or a number representing a list. 0=L1, 1=L2, 2=L3, et cetera

I didn't mean to include them because I haven't added an error handler for if #Elements is 0. Don't let it be 0!!

Hmm, that is odd. I will have to see what is up with that... Also, for that, you can use command 21 which automatically copies to a string

I know, I was using that to show off the speed of the rectangle operations. I could just take out key presses, but I don't want to