Why are locking size and position treated as one?

Mark Swindell mdswindell at cruzio.com
Fri Feb 5 10:35:55 EST 2010

I asked this a couple of days ago and got no response so I thought I'd try again.

Why are locking size and position of an image inextricably linked?  They seem to me to be two separate entities.  I know how to get around the situation via script, but I don't know why there should be the inconvenience of having to "get around" anything.  Is there a good reason for this or is it just a legacy reality that could be changed?  Why not be able to drag an image around whose size is constrained?


More information about the Use-livecode mailing list