Issues with num.ToStr

Martin Hebel

I'm using the following code in a very basic graphics program - not much esle going on.

    gr.textmode(2,2,6,3)
    gr.text(50,50,num.ToStr(30,num#DEC))
    gr.text(150,50,num.ToStr(56,num#DEC))

What I get on the screen is 36 and 56 instead of 30 and 56.· There's a problem it seems in Jeff's numbers that I can't find a work around for. In another program, the 6 on 56 doesn't even show up.· Any thoughts?

-Martin
·

Rayman

I think you have to use, e.g., "num#DEC5" instead of "num#DEC"...

deSilva

GRAPHICS works "in parallel" - commands generally return before the action is completed. As gr.text takes "a little bit" of time the internal buffer of NUM - used twice! - will be overwritten in the meantime.

It will most likely help to call
gr.finish

---

Edit: As you know well, Martin: The issue is always the program you suspect least: your own

Post Edited (deSilva) : 12/14/2007 3:27:24 AM GMT

Martin Hebel

Sorry for the lack of response here, deSilva was correct. The student working on the project figured it out before I did by inserting some delays, and once he told me about that, the light shone through. There's a gr.Finish? Hmmm, I'll have to look for that [noparse]:)[/noparse]

It seems like I ran into the same problem a year ago, then forgot about it.

But uless I misread the 'num#DEC2' usage, I still can't force leading 0's. The modifier simply shows that digit alone. But, did a work around for that one.

THanks much,
Martin

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
SelmaWare Solutions - StampPlot GUI for controllers, XBee and Propeller Application Boards

Southern Illinois University Carbondale, Electronic Systems Technologies

American Technical Educator's Assoc. Conference·- April, Biloxi, MS. -- PROPELLER WORKSHOP!