Occams razor applies here I think. (well probably it wasn't intended this way but what the heck)
If you can fix something in a simpe way than why mess about with complex stuff.
Changing all variables from integer to long isn't that difficult and it might even speed up the program since we can lose a lot of limits which at present are set to 32000 only because that is all an integer can handle. It is also quite possible that windows (a 32 bit environment) could well process long variables more efficiently and quicker than integers.
I did a few experiments with running robot memories as longs. It took about 10 minutes to convert and ran just as quick as it does now. The only reason I temporarily abandoned it was because I didn't have time to update every single subroutine that demands an integer input from the call. That would take a couple hours or more.
Bots, that sounds like a scaling system which although it wil work in theory, will cause a shit-load of grief at much larger screen sizes for robots like Ant-Bots who need a precise destination to return to the queen.
As I explained before, in a sim at size 1000 (1000 times bigger than standard), the coordinates would run from 0 to 9,000,000 along the x axis. If we use a scale factor of 1000 to keep the .xpos variable at 9000 then it will eventually become difficult for the ant to find its queen. When the robot is at position x=9,000,000 it will actually have more than 10 robot-widths at that loaction. It may never find the queen at all.
However with longs, it is trivial to return a value of 9,000,000 to .xpos.
:D PY :D