On 11/21/2014, 6:08 AM, Graham Samuel wrote:
When I switched from LC 6.x series to 7.x, I assumed my ‘saves’ would
save in the new format. They didn’t. That explains a lot. I suppose
everyone else here already knows that you have to do a ‘Save As…’ to
get the new format - but just in case…
I th
On Nov 21, 2014, at 5:08 AM, Graham Samuel wrote:
> Just FYI, I just got this from the mother ship. I was under the impression
> that the system property
>
> the stackFileVersion
>
> showed the file format (7.0 or earlier) of the currently open stack. It
> doesn’t: all it shows is the format
Just FYI, I just got this from the mother ship. I was under the impression that
the system property
the stackFileVersion
showed the file format (7.0 or earlier) of the currently open stack. It
doesn’t: all it shows is the format that any new stack will have when created
in the IDE. To find ou
Thanks for that thought Peter. RunRev are now on the case, but I still have not
absolute confirmation that it's a bug. I did check that my stack is using the
7.0 file format (if it wasn't, it would be easy to see what went wrong). I'll
report here when I get more info.
Graham
> On 20 Nov 2014,
Graham
It may be that that whilst string data processed by our LiveCode scripts and
handlers is Unicode that is not the case with UI objects. I think that there is
a chance that LiveCode is still using native encoding (Windows Code Page on
Windows, ISO-8859-1 on Linux and the truly venerable Ma
I’ve got a strange problem that (so far) I haven’t been able to reduce to a
simple recipe.
I’m using a few Unicode characters in some menus in a cross-platform app (I
mean special characters that don't appear on a Windows keyboard - I do realise
that everything in LC is Unicode now). In this in
