2010-06-03, 07:29 AM
I think your code is probably best. But perhaps for basic things this code is very simple, and is better than traditional print.
I guess future versions of this routines add height, wide, activity, phase, direction, collision, addr_way_to_go and others parameters in the fastcalls or subs, perhaps using ix+0 and looping all the chars(wide x height).
We´re making proves, trying the best for every case.
Make our contributions.
I guess future versions of this routines add height, wide, activity, phase, direction, collision, addr_way_to_go and others parameters in the fastcalls or subs, perhaps using ix+0 and looping all the chars(wide x height).
We´re making proves, trying the best for every case.
Make our contributions.