> It does indeed to seem like a power of two issue, since lots of tests i've > come up to a working point size/font/string length that works for an fps > counter, but other than cudging that data together yourself (i would suppose > there's a formula if you know the size/font/way font is rasterized to a > texture to tell what the legal string length would be, and pad from there) > is the only way i can see to get this workaround happening.
Something tells me that it's not designed for the text to change after the initial setting... or it was a "feature" that is no longer supported. Please can we have this working again?! It's -very- useful for debugging Marc ==========================================================================To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
