I missed it but apparently there's something in the 7.0 release notes about it. It's a new property of the player control.
Pete lcSQL Software <http://www.lcsql.com> Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html> On Fri, Oct 31, 2014 at 9:52 AM, Graham Samuel <livf...@mac.com> wrote: > Thanks Pete - so Mark will certainly have to modify his button stuff. > Meanwhile I guess I can cheat by changing ‘status’ to ‘status1’ throughout > the code for these objects. > > It will be interesting to find out what RunRev is using this word for - > kind of sounds like it should be reserved, doesn’t it? > > Graham > > > On 31 Oct 2014, at 00:44, Peter Haworth <p...@lcsql.com> wrote: > > > > Hi Graham, > > Late to this one but there is indeed a new property named "status" which > is > > why your script now fails. Unfortunately, can't tell what it's used for > > since there's no dictionary entry for it. About to file a bug report for > > that. > > > > Pete > > lcSQL Software <http://www.lcsql.com> > > Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and > > SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html> > > > > On Sat, Oct 25, 2014 at 6:26 AM, Graham Samuel <livf...@mac.com> wrote: > > > >> In a desktop app (Mac and Windows - currently testing the Mac version) > I’m > >> using a button (actually a group acting as a button) designed by Mark > >> Schonewille which does nice things with shading. This has been working > for > >> a long time, ever since it was announced by Mark. Now in LC 6.7, I get a > >> compile error in a setProp handler in the group (in fact in several > groups > >> with the same script). Part of a case statement looks like this > >> > >> … > >> lock messages > >> set the status["disabled"] of me to not theBool > >> set the status["hilite"] of me to false > >> unlock messages > >> … > >> > >> The IDE reports > >> > >>> compiling at 2:58:22 PM > >>> Type Expression: bad factor > >>> Object ClearAllGroup > >>> Line set the status["disabled"] of me to not theBool > >>> Hint [ > >> > >> There is no hint. As it would seem to be a syntax failure, maybe some > new > >> reserved word is getting in the way - but this is just a guess. > >> > >> I have not yet been able to isolate this to confirm and then report it > as > >> a bug. Mark, if you're around, do you understand what's happening? I > quite > >> understand if you haven't got time to look at it, but I thought I'd ask > >> before trying to go deeper into the issue. > >> > >> TIA > >> > >> > >> > >> _______________________________________________ > >> use-livecode mailing list > >> use-livecode@lists.runrev.com > >> Please visit this url to subscribe, unsubscribe and manage your > >> subscription preferences: > >> http://lists.runrev.com/mailman/listinfo/use-livecode > > _______________________________________________ > > use-livecode mailing list > > use-livecode@lists.runrev.com > > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > > http://lists.runrev.com/mailman/listinfo/use-livecode > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
