I wonder why we have both lockUpdates and boundingRect. They seem very
similar.
On 6/13/17 7:54 PM, Scott Rossi via use-livecode wrote:
Keep in mind, there’s also the lockUpdates property of groups, which while
differing mechanically “under the hood”, essentially causes the same perceived
result — while enabled, a group’s rect is not changed when its child objects
are resized/repositioned.
I don’t know how all these are verbosely named since I also use the default
property names.
Regards,
Scott Rossi
Creative Director
Tactile Media, UX/UI Design
On Jun 13, 2017, at 3:37 PM, Devin Asay via use-livecode
<use-livecode@lists.runrev.com> wrote:
On Jun 13, 2017, at 4:19 PM, Devin Asay via use-livecode
<use-livecode@lists.runrev.com> wrote:
Yes, in essence. If you have a group and set the clipsToRect property to true
(there’s no way to set it in the PI yet—that’s what I’m going to add), you can
then change the rect of the group, and the group will *not* automatically reset
its rect to the size of the child controls + margin. It is persistent, even if
you leave the card or close the stack. Yet the group’s position and size
remains unlocked so you can quickly select and change the group’s rect if you
want. A nice feature when you need it.
ClipsToRect is the property name. So what “plain language” label do you think
would be best for the PI?
How about “Prevent auto-resize of rect”?
Devin
On Jun 13, 2017, at 4:11 PM, Phil Davis via use-livecode
<use-livecode@lists.runrev.com<mailto:use-livecode@lists.runrev.com>> wrote:
So it's about manually updating the rect vs. having it in an auto-update mode?
Phil Davis
On 6/13/17 3:01 PM, Devin Asay via use-livecode wrote:
So far I’m kind of partial to Scott R’s “Persistent rect”. Conversely, it could
be something like “Auto-update rect”, but then the checkbox would be opposite
the property setting. That’s almost as bad as something like dontUpdateRect.
(Sorry, Scott, plug your ears.)
Devin
On Jun 13, 2017, at 3:34 PM, J. Landman Gay via use-livecode
<use-livecode@lists.runrev.com<mailto:use-livecode@lists.runrev.com><mailto:use-livecode@lists.runrev.com>>
wrote:
On 6/13/17 4:17 PM, Jim Lambert via use-livecode wrote:
or
‘Clip Group to rect’
There are a few others like that, where the explanation is just the original
term (or close) with spaces added. I always felt that didn't explain much. But
the suggestion does have company in the PI.
Devin Asay
Director
Office of Digital Humanities
Brigham Young University
_______________________________________________
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
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.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
