I am updating an application written in 5.2.4 to 5.5 and with no
modifications it turned all my drawstring unicode double byte text into
"?"'s...
After confirming that the text was arriving "safely" I started turning
various things on and off... what "fixed" it was turning off the
"useoldrenderer"...
I searched the bugbase but could not find an existing description of
this issue. I will try and isolate it in a small application, but has
anyone else had their drawstring code "break" when they went to 5.5.
from 5.2.4 and were using useoldrenderer to try and get some speed?
My example
tempict=newpicture(canvas1.width,tempheight,32)
tempict.graphics.useOldRenderer=false
tempict.graphics.foreColor=mytextcolor
tempict.graphics.textfont=myfontname
tempict.graphics.textSize=myfontsize
tempict.graphics.drawString myinbuffer,0,0,canvas1.width
works
tempict=newpicture(canvas1.width,tempheight,32)
tempict.graphics.useOldRenderer=true
tempict.graphics.foreColor=mytextcolor
tempict.graphics.textfont=myfontname
tempict.graphics.textSize=myfontsize
tempict.graphics.drawString myinbuffer,0,0,canvas1.width
does not... the characters, if double byte, come out as garbage....
Thanks!
Todd Fantz
tfantz at mindspring dot com
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|