On 2015-09-03 21:38, J. Landman Gay wrote:
Returning to this topic...we are in the process of creating new stacks
in LC 7 while still running older LC 6 stacks with the same app.
Stacks have custom properties containing text created on a Mac, and my
app uses MacToISO() to display the text when
Not an ellegant approach but have you considered having a custom
property in your stacks that identify them for you. It sounds like
you are in control when those stacks are created and updated, so it
might work.
RObert
On 04.09.2015 at 13:38 Uhr -0500 J. Landman Gay apparently wrote:
Barring
On 9/4/2015 7:57 AM, Mark Waddingham wrote:
From what you are saying you want people to be able to edit content in
both LC6 and LC7, the content itself being saved in LC6 format. i.e. You
want to move your system forward to LC7, but you need to still support
LC6 clients and editors. Is that
On 9/4/2015 1:46 PM, Robert Brenstein wrote:
Not an ellegant approach but have you considered having a custom
property in your stacks that identify them for you. It sounds like you
are in control when those stacks are created and updated, so it might work.
It hadn't occured to me, actually. I
Returning to this topic...we are in the process of creating new stacks
in LC 7 while still running older LC 6 stacks with the same app. Stacks
have custom properties containing text created on a Mac, and my app uses
MacToISO() to display the text when running on Windows.
Some of the LC 6
LC 7 knows the difference between binary and text - this is retained when
saving custom props (if you save in 7+ format).
The only rub is that for existing stacks in the old format custom props will be
taken to be binary data (which auto converts to text assuming the native
encoding). Thus you
Hi Dan,
Not exactly. All text is now unicode. If you set a custom property to
the text of a field, it is unicode already. When you set the text of a
field to a property, it is again unicode. This avoids the need for
mapping and other hacks.
I haven't tested this much. I can imagine that
Hello! Way back in LiveCode 5 and 6, custom properties were not ported to the
proper character set when you opened the stack on a different platform (Mac --
Win or Win -- Mac). This was easily solved by a simple macToISO() or
ISOtoMac(). However, it appears that LC 7.x is now doing this
