LiveCode Forums.

The color and border settings for pop up menu buttons and their popped up menus are inconsistent.

textColor, fillColor, and font selections work for both the pop up button and the popped up menu.
HilitedText, Top 3D Bevel, and Bottom 3D Bevel only works for the popped up menu, not the button.
DropShadow only works for the button, not the menu.

What's interesting is that most seem to work better for the other menuModes, although I didn't test exhaustively.

I suggest there be a mechanism to access the popped up menu properties. My suggestion would be to show the popped up menu object when a) the Edit tool is selected, and b) when a check box named "Popup inherits button properties" in the base button's properties is unselected. Then the popped up menu can be selected and have separate properties.

For scripting, I suggest the popped up menu be a field type (which I assume it already is under the hood), be addressed as "field 1 of btn "myPopUpButton", and have a default script (just as the menu button does for menuPick) that has the existing actions visible - on mouseOver hilite the mouseChunk, on mouseUp send menuPick to me with the mouseText, on mouseLeave hide me, etc.

Walt

The question bantymon had about skinning tab panels applies to this as well - an ability to get at the underlying components of assemblies like this. Tab panels, popups, scroll bar components, all would benefit from being able to unlock their Property Inspector so their underlying "group" can be edited.
Walt