These types of groups will cause you to lose your calculation definitions as well as being slower to work with the sub-objects.Įven simple groups that don’t have an additional button or hide definitions will incur delays just because you’ll have to un-group and then re-group the items. Breaking the group apart causes you to lose the hide condition or button definition on the group – at least FM was nice enough about it and would warn you that you were going to lose something when breaking the group. It’s a group of 1 object, but still a group.) In FileMaker Pro Advanced 16 you could apply a hide condition to a group, but then if you needed to edit one of the objects in the group, you had to un-group those items in order to make those edits. (To make it a button FileMaker makes it into a group, first. There is a double whammy when there is a Hide Condition applied to a group, or a button action has been applied to non-button objects, e.g. Now you can do all those adjustments without having to break the group and then re-group the objects when you are done! But then you might have to make a change to a font, or a hide condition, or a small tweak to the position of one item within the group. a custom calendar picker, or custom labeling for a radio button set, a set of fields for an address, etc), and you want to keep them all together in a particular arrangement. Say you have a set of fields and objects that together make up a ‘widget’ or function (e.g.
I often group many things together to aid in layout setup and positioning.
How many times have I been annoyed and delayed by having to ungroup something just to make a simple edit? Too many to count.
0 kommentar(er)
