Thank you for the post.
I am unable to reproduce the issue. To attempt to reproduce, I performed the follow actions:
1. New Database with a single field.
2. Created a button grouped with a text object to run a script.
3. In layout mode, used control drag to copy the button.
4. With copied button selected: right-click > Arrange > Ungroup
Am I missing something to reproduce? Perhaps, to reproduce requires a specific group of object types?
Interesting. This is much more subtle than I thought. ctrl drag has nothing to do with it. I can reproduce the issue with copy and paste. In fact, duplicating the button is not required. I can get this to happen with the original button. And it doesn't have to be a button, just grouped.
Here's what I had to do to reproduce:
Drag the grouped objects past the right hand edge of the layout. Release the mouse, drag the group back. Or leave the group outside of the layout boundaries. DON'T right click the group, try ungrouping from the Arrange menu or the inspector. If you right click the group, not only is ungroup available in the arrange sub menu, but when you release the mouse button and check, ungroup has now become available from the other two sources of this option. Saving your layout changes corrects the issue. Selecting a different object and then selecting it again fixes the issue.
So this happens with a vary specific set of steps and even the slightest variation will keep you from reproducing the issue.
This issue is a much bigger problem when working with layouts for the iPhone as you are then much more likely to be dragging groups of objects outside the layout boundaries while you edit the layout.
Excuse me if i misunderstood, but Phil's expected behavior is only valid with FMP v11 and prior converted file's buttons.
I think that a brand new v12 button can never be ungrouped.
What am i missing ?
Fred, I'm using brand new, never converted files for this.
All buttons are actually grouped objects where you group the visible object with an invisible "button" object that contains the button setup options you select for the button. When you ungroup a button, the invisible button object is deleted, but the visible object--which could be nearly any layout object, a field, a block of layout text, a graphic image.... remains but no longer functions as a button unless you use button setup to once again group the object with a new invisible button object. When you use the button tool to add a button, the same process happens, but FIleMaker saves you a step by automatically opening button setup for you.
In my original case, I had a field and it's layout object grouped to become a button so that it could be tapped on the screen to perform a script. That was three objects, the text label, the field and the invisible button object grouped to form a button. I encountered the issue when I then decided to make the field label a button that performed a script to sort the records and the leave the field as the button to perform the original script. When I went to ungroup them, I couldn't.
Thank you for the assistance in narrowing this down.
I am now able to reproduce with a new file. The key to replication was to first drag the grouped objects passed the layout boundary on the right. Afterwards, simply click the Inspector's Appearance tab and then click back to the Position tab. The ungroup button now appears greyed out in the Inspector.
The issue appears to be Windows specific. I can replicate with FileMaker Pro 12.0v4 on Windows 7, but I was not able to replicate on Mac OS X 10.7.5.
I forwarded a full report to Testing and Development for review.
Thank you for your patience and further explainations : i didn't understood that your button were not created with the button tool.
More, i never realized that the ungroup action could be used to remove button's definition when only one object was visible. Thanks again !
However, on FileMaker 12 versions, the button tool is no longer working like you are saying above. New buttons are "real" button objects, that cannot be ungrouped. That is the main reason why i misunderstood your original post.