mark at livecode.com
Thu May 18 14:44:20 CEST 2017
On 2017-05-18 13:29, hh via use-livecode wrote:
> No, not only the binary-level compatibility is the problem. LC Builder
> is not downward compatible (without documenting that), already running
> parts are removed.
> See for example (in forum/bug-triage):
I have to remind people - please file bug reports! If you don't then the
chances of these things getting addressed, explained, or advice given
The issue there I'm pretty sure is purely one of non-binary
The module files generated by the lc-compile tool in any major version
is likely to only
produce files what work in that major version.
(It does sound like a bug has crept in there, potentially, in resource
resolution though - hence my comment about filing bug reports).
So the problem actually reduces to - having a widget which does not use
anything new in LCB V+1, but you want to use in V and V+1. This is
by compiling the widget file with the lc-compile from V and the
If your widget uses new LCB features which are only in V+1, then
compatibility isn't going to work - like it wouldn't in a stack which
to use features in 9, which aren't in 8.
Mark Waddingham ~ mark at livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps
More information about the use-livecode