No announcement yet.

putnum formatting

  • Filter
  • Time
  • Show
Clear All
new posts

  • putnum formatting

    Another question for the experts here. Does the leading space bit on the really bad ascii graphic explanation of the putnum function actually work. I cannot make it function under any circumstance.
    I ended up having to do this to make it work:
    if (CurrentData[15] >= 0)
    gfx_MoveTo(68, 45) ;
    putnum(45834,CurrentData[15]) ;
    gfx_MoveTo(60, 45) ;
    putnum(45834,CurrentData[15]) ;

    Also, can a bit list version of that graphic please replace the ascii one? The context help and the pdf don't match or line up and it is confusing.
    something like:
    bits 0-4 Number base (usually 2,10 or 16)
    bits 5-8 Reserved
    bits 9-11 Displayed digit quantity
    bit 12 Leading zeros (1=Zeros included, 0=Zeros suppressed)
    bit 13 Blanking (1=Leading zero blanking, 0=Show Zeros)
    bit 14 sign bit (0=signed, 1=unsigned)
    bit 15 Leading spaces (1=space before signed number, 0=No space)

    I'm really not sure this is correct but it is what I'm going with until someone corrects it.

    If email spam were the edible Spam, there would be no world hunger.

  • #2
    Sorry, it does not work, thanks for reporting it.

    As it is the only known issue on the current PMMC and it affects only you can you tell me which display you are currently using so I can generate a 'special' PmmC for you.

    BTW it might be clearer if you used, say DEC3ZB | 0x8000 for the format.

    We will get the manual and context help updated

    The Reserved is 5-7 and the Display digit quantity is 8-11, but I think you realised that


    • #3
      Hi, I am using the uLCD-32032-P1T
      I did try the DECxZB options rather than the custom number before trying to fix it with a bit combo of my own. I thought for certain I was doing it wrong.

      Thanks for the clarification on the bits.

      If email spam were the edible Spam, there would be no world hunger.