POST does not work under lock messages

Brian Milby brian at
Fri Jan 8 11:05:50 EST 2021

The docs don’t list all messages but do say that navigation and object creation messages are not sent.  It gives a couple examples of each.  This is in addition to get/set prop.

Sent from my iPhone

> On Jan 8, 2021, at 6:33 AM, Neville Smythe via use-livecode <use-livecode at> wrote:
> It took me a while to figure this one out. I have a number of scripts which POST to LiveCode Server .lc scripts. All were working fine except one which always returned the output from whatever POST had last been executed. Evidently the previous form request was being resubmitted. Turns out I had a lock messages command before calling POST. 
> Seems to me that shouldna oughta happen —either it’s a bug, or it should be documented 
> (I think there is a documented warning about DataGrids needing Lock messages off? And wasn’t there a discussion a while back about Lock messages needing levels? The current documentation for Lock messages says it blocks “setProp triggers, getProp and certain other messages” where “certain”  is left undefined.)
> Neville
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the use-livecode mailing list