Re: Feeling a bit "NumToCharred"...
Richmond- Right, then. It's BZ #8504. -- -Mark Wieder mwie...@ahsoftware.net ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Feeling a bit "NumToCharred"...
On 19/12/2009 01:10, Mark Wieder wrote: Richmond- Friday, December 18, 2009, 1:36:16 PM, you wrote: I wasn't aware it might be a bug until Mark Weider pointed it out; I suppose whether or not it's a bug is a matter of POV, but to me the docs seem to more than imply that non-double-byte chars will be converted as part of the "set the unicodetext" process. Reporting an error would also be ok. Ignoring the "standard" xTalk catenation syntax seems like a bug. I'm happy to do the honors if nobody else wants it. I would be most grateful if you could do that. ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Feeling a bit "NumToCharred"...
Richmond- Friday, December 18, 2009, 1:36:16 PM, you wrote: > I wasn't aware it might be a bug until Mark Weider pointed it out; I suppose whether or not it's a bug is a matter of POV, but to me the docs seem to more than imply that non-double-byte chars will be converted as part of the "set the unicodetext" process. Reporting an error would also be ok. Ignoring the "standard" xTalk catenation syntax seems like a bug. I'm happy to do the honors if nobody else wants it. -- -Mark Wieder mwie...@ahsoftware.net ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Feeling a bit "NumToCharred"...
On 18/12/2009 22:02, Mark Schonewille wrote: Hi Richmond, If you use uniencode(space) or numToChar(32), it is solved. I'm not sure that this is a bug. I wasn't aware it might be a bug until Mark Weider pointed it out; more, one of the many differences between the documentation and the RAD . . . :) What I am a bit cheesed-off about is that if I want to put characters I can access with my standard keyboard (U.S. extended) into a unicode 'sentence' in a field I have to encode those indivdually (including the spaces) using numToChar rather that just typing '+' or 'Q', as in: set the useUnicode to true set the unicodeText of fld "GUFF" to numToChar(9012) & " this whole things gets on my nerves" which is CONSIDERABLY easier than: set the unicodeText of numToChar of fld "GUFF" to numToChar(9012) & numToChar(32) & numToChar(funnyNumber) & numToChar(funnyNumber2) & numToChar(funnyNumber3) & numToChar(funnyNumber4) ad nauseam ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Feeling a bit "NumToCharred"...
Hi Richmond, If you use uniencode(space) or numToChar(32), it is solved. I'm not sure that this is a bug. If you want to use space as a delimiter in a binary stream consisting of uniencoded bytes, you might have a problem if && suddenly equals a uniencoded space. Of course, one might as well use a different delimiter --and one probably should. I think I would do something like the following: function toUnicode set the useUnicode to true repeat with x = 1 to the paramCount if param(x) is a number then put numToChar(param(x)) after myUnicode else put uniencode(param(x)) after myUnicode end if end repeat return myUnicode end toUnicode You can call the function as follows: set the unicodeText of fld "Foo" to toUnicode(7749," a b c d") I haven't tested this particular script, but such a solution might work, is quite easy to use and doesn't slow down things much. -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering Homepage: http://economy-x-talk.com Twitter: http://twitter.com/xtalkprogrammer Full PayPal integration and automation in web site or (Revolution/ SuperCard/other) software. Contact me for a quote before 1 Jan 2010 and we'll charge (reduced) 2009 prices. http://economy-x-talk.com/contact.html Op 18 dec 2009, om 20:16 heeft Richmond Mathewson het volgende geschreven: Wl, here I go again; replying to my own message: useUnicode throws a tantrum with "&&", as it does with " ", so everything (which is incredibly tedious) has to be down the numToChar way (i.e. no mixt forms): on mouseEnter set the useunicode to true set the unicodeText of fld "GUFF" to numToChar(7749) & numToChar(32) & numToChar(43) end mouseEnter --- What a pain in the bum! To my mind a mixt syntax, whereby characters accessible only via numToChar could be mixt with those directly accessible via the keyboard would be more intuitive. Compare: set the unicodeText of fld "GUFF" to numToChar(7749) && "a b c d." to set the unicodeText of fld "GUFF" to numToChar(7749) && "a" && "b" && "c" && "d" & "." to set the unicodeText of fld "GUFF" to numToChar(7749) & numToChar(32) & numToChar . . . . . . . . . . . . frankly cannot even be bothered to work it out . . . time for some coffee . . . z z z --- A mixt syntax would save me (even if no-one else) hours and hours of typing, fiddling around with unicode numbers for trivial characters, and merry repetitive stress injury. ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Feeling a bit "NumToCharred"...
Richmond- Friday, December 18, 2009, 11:16:47 AM, you wrote: > useUnicode throws a tantrum with "&&", as it does with " ", so > everything (which is incredibly tedious) has to be down the > numToChar way (i.e. no mixt forms): > on mouseEnter > set the useunicode to true > set the unicodeText of fld "GUFF" to numToChar(7749) & numToChar(32) > & numToChar(43) > end mouseEnter You should report this as a bug. The doc comments for setting the unicodeText of a field state that any non-Unicode chars are converted to single-byte chars to save storage, and this is obviously not happening. -- -Mark Wieder mwie...@ahsoftware.net ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Feeling a bit "NumToCharred"...
Wl, here I go again; replying to my own message: On 18/12/2009 19:58, Richmond Mathewson wrote: I popped this in a button: on mouseEnter set the useunicode to true set the unicodeText of fld "GUFF" to numToChar(43) end mouseEnter and I get a '+' in fld "GUFF" - exactly as wanted. BUT . . . on mouseEnter set the useunicode to true set the unicodeText of fld "GUFF" to numToChar(7749) && numToChar(43) end mouseEnter does not give me char 7749, a space and a '+'; it only gives me char 7749 and a space I wonder why? Probably my syntax is incorrect . . . -- useUnicode throws a tantrum with "&&", as it does with " ", so everything (which is incredibly tedious) has to be down the numToChar way (i.e. no mixt forms): on mouseEnter set the useunicode to true set the unicodeText of fld "GUFF" to numToChar(7749) & numToChar(32) & numToChar(43) end mouseEnter --- What a pain in the bum! To my mind a mixt syntax, whereby characters accessible only via numToChar could be mixt with those directly accessible via the keyboard would be more intuitive. Compare: set the unicodeText of fld "GUFF" to numToChar(7749) && "a b c d." to set the unicodeText of fld "GUFF" to numToChar(7749) && "a" && "b" && "c" && "d" & "." to set the unicodeText of fld "GUFF" to numToChar(7749) & numToChar(32) & numToChar . . . . . . . . . . . . frankly cannot even be bothered to work it out . . . time for some coffee . . . z z z --- A mixt syntax would save me (even if no-one else) hours and hours of typing, fiddling around with unicode numbers for trivial characters, and merry repetitive stress injury. ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Feeling a bit "NumToCharred"...
I popped this in a button: on mouseEnter set the useunicode to true set the unicodeText of fld "GUFF" to numToChar(43) end mouseEnter and I get a '+' in fld "GUFF" - exactly as wanted. BUT . . . on mouseEnter set the useunicode to true set the unicodeText of fld "GUFF" to numToChar(7749) && numToChar(43) end mouseEnter does not give me char 7749, a space and a '+'; it only gives me char 7749 and a space I wonder why? Probably my syntax is incorrect . . . ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
