It sounds like something somewhere is changing that data to a native string
before being textDecoded. Try putting in some logging of the value of
'tData is strictly a binary string' to find out where it is getting
stringified.
On Fri, 22 Jun 2018 at 18:39, Tom Glod via use-livecode <
use-livecode@
hey malte . the custom properties and array encoding changed with v7
its safe to say that is the cause of any issues with character
encoding. ...i store binaries and strings in custom properties . so i
think internally it would make sense that its a binary.
On Thu, Jun 21, 2018 at 5
Hi all,
I am a little bit puzzled. a stack I started way back in engine 4.x always
had a custom property set with multiple UTF8 encoded strings. Those were
transferred just fine from Mc to PC and the UTF8 strings remained intact.
Somewhere down the road something seems to have changed. When
Random thougth of the day:
What i always found weird is, the imagedata has a space for alphadata in
itself. it's 4 bits for each pixel, and thus has space for the three colours:
rgb and alpha too... but the fourth one just is always zero.
Meanwhile the text property can't be modified by script,
That's a fact I never understood. Thanks Scott!
Phil
On 2/3/11 5:06 PM, Scott Rossi wrote:
the text property of an image can refer to
both its image and alphaData together.
--
Phil Davis
PDS Labs
Professional Software Development
http://pdslabs.net
Recently, Tim Lambert wrote:
> Using 4.5.3 and have a single cd with 20 or 30 itms in a selectable list.
> Clicking on a line brings up the corresponding image by setting the imagedata
> to the corresponding custom prop of the cd. In OSX and on the iPad simulator
> this works fine. The standalone
Hi
Using 4.5.3 and have a single cd with 20 or 30 itms in a selectable list.
Clicking on a line brings up the corresponding image by setting the imagedata
to the corresponding custom prop of the cd. In OSX and on the iPad simulator
this works fine. The standalone OSX also works fine, but the Win
