Re: [ANN] Release 9.0.1 RC-1
Andy: LiveCode on Windows is now usable! No lag when the message box and the Project Browser are is use. Wow, I'm going to try it in a few days when I have a chance! About time too - a little less Winphobia and Windistance goes a looong way and helps keep in touch with a huge portion of our end users. Great news. :) Best wishes, Curry Kenworthy Custom Software Development LiveCode Training and Consulting http://livecodeconsulting.com/ ___ 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
Re: OS EOL (was: [Bug 19998] The non-appearance of Polygon graphics in LC)
An older system offline could be useful for many things. People have used old computers even to get paralyzed people back in the game with speech. It could also run special projects, education or a kiosk. Be careful though. A new system fully patched still could be risky online if people always trust the status quo and what's popular, without thinking it through. Some things (like security patches) are popular for very good reasons. But other things not so much. The powers that be can only protect you to an extent - and sometimes we need protection from the powers that be. To survive and thrive, we need independent thinking too. Best wishes, Curry Kenworthy Custom Software Development LiveCode Training and Consulting http://livecodeconsulting.com/ ___ 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
Re: Sender of send in time
> On Jul 13, 2018, at 1:26 AM, hh via use-livecode > wrote: > >> Bob S. wrote: >> Something in my scripts is sending a selectionChanged message in >> time to a specific datagrid when it shouldn't. How do I determine >> the sender of a send in time message? > > Simply use a a parameter: > > send "selectionChanged " to in > > where identifies the sender. > Or, if you don’t want to create such parameters to identify your senders, you could use the executionContexts: send "selectionChanged item 2 of line -1 of the executionContexts" to in Or, if you want to reduce clutter in your many senders, you could just: send "selectionChanged the executionContexts" to in — Dick ___ 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
