Quote: "But doesn't anywithin take a 0 or 1 value? "
Yeah, and each state can have one.
True (1) = go to the next state (which 'hides' the last number and 'shows' the next one)
The Inc and Dec have to be tied together (ifused) to stay in synche.
Activated states would adjust opposite **crementors.
Edit
After I finish moving, I plan to work on this full time.
I've been dreaming and scheming this thing in my head way before we could move to targets.
I need this for my FPSRPG. I may even drop out of school for a quarter. (to play with FPSC-X10)
This move should result in a faster conection and new puter for X10.
I'm going to get jiggy with FPSC very soon.
~
~ MWUHAHAHAHAHA
- - - - -
Second Edit
I had another idea.
By determining the distance away, one object could determine all the digits.
The placement objects would be inline with the determiner at the end.
This way one one object would be scripted. The placement objects could use default.fpi.
This way may be better. I know this all sounds crazy, but I have to find this workaround.