<soapbox> The most important rule to follow when establishing any new property should be: Don't use "dont".
The application of a "negative property" should never have been established (dontWrap, I'm talking to you). Properties should always be non-negative and simply enabled or disabled depending on the default behavior. </soapbox> In this case, I get that you're referring to readable label, so there's more flexibility here of course, I just needed to vent :-) The above said, you're right, this is a tricky case. IMO the real differentiation here is that the rect of the *unlocked* group remains unaffected by the locations of its child objects. Since you know the control is a group, maybe the verbose label is something like "persistent rect" since the rect will, for the most part, remain constant. Maybe I'm forgetting something... Scott Rossi Creative Director Tactile Media UX/UI Design > On Jun 13, 2017, at 9:27 AM, Devin Asay via use-livecode > <use-livecode@lists.runrev.com> wrote: > > > On Jun 12, 2017, at 11:45 PM, Mark Waddingham via use-livecode > <use-livecode@lists.runrev.com<mailto:use-livecode@lists.runrev.com>> wrote: > > On 2017-06-12 22:22, Richard Gaskin via use-livecode wrote: > For group controls you will find that it is. Try it. It's quite handy. > > Another useful thing which I'm not sure is particularly visible (but is in > the dictionary!) is the group 'clipsToRect' property. > > When 'the clipsToRect' is set to true you get a group which acts like > lockLocation is set, but is resizable. In this case the group's size is > determined purely by the rect it has set, and not the union of the rectangles > of its children. > > This might have been mentioned somewhere else in this thread, but its > probably worth repeating if so as a group with clipsToRect true, and a > resizeControl handler makes a good base for a custom control. > > It’s not visible in the PI, but it’s not hard to add. I’d be happy to make a > pull request for it. The main question is what would be the “readable label” > of this property? (My current favorite is the first one.) > > - Group rect remains fixed > - Fixed group rect > - Lock group rect > - Group rect is fixed > - Don’t change group rect > - Group rect is independent of child controls > - Prevent group rect size when child objects move or resize > > It’s a tricky balance between clear enough and short enough. > > Ideas? > > Devin > > > > 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 _______________________________________________ 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
