I wouldn't make a loop variable a Type field. I understand you are trying to gain speed that way, but that kind of optimisation can lead to tangles down the track - eg calling one of your methods within another method's loop. I doubt you'd notice any speed difference using locals in the above.
I'd have some kind of capitalisation consistency happening - so you can easily distinguish between locals, fields and globals.
You might find ordering your functions/methods alphabetically handy.
Finally I tend to allocate one .bmx file per Type as a general rule. Makes for a lot of files but I find my code easier to navigate that way.
But this is just my personal preference. I'm sure there are plenty of others out there that'd disagree with one or more of the above.
I'd have some kind of capitalisation consistency happening - so you can easily distinguish between locals, fields and globals.
You might find ordering your functions/methods alphabetically handy.
Finally I tend to allocate one .bmx file per Type as a general rule. Makes for a lot of files but I find my code easier to navigate that way.
But this is just my personal preference. I'm sure there are plenty of others out there that'd disagree with one or more of the above.