Alain, you have done it! Thank you!

Where you learned to do this:

> Appearance Button _cAction, _activeBtn,_actionMenu,¬
>  _kControlBehaviorCommandMenu,,"Action", (275,27)-(330,45),¬
>   
> _kControlBevelButtonSmallBevelProc_kControlUsesOwningWindowsFontVariant

(the _kControlBehaviorCommandMenu part)

and this:

> Def GetButtonData( btnID, _kControlMenuPart, ¬
>                   _kControlBevelButtonLastMenuTag, ¬
>                    Sizeof(SInt16), @menuSel.v%, actualSize )
>
> Def GetButtonData( btnID, _kControlMenuPart, ¬
>                   _kControlBevelButtonMenuValueTag, ¬
>                   Sizeof(SInt16), @menuSel.h%, actualSize )

is beyond me, but I am very grateful you have shared it.

> Now the tricky part is that the end user interaction is reported as a  
> _btnClick dialog event. The prog intercepts the event more or less  
> like so:

Actually, for me this part is no problem because I was already prepared  
to handle these popup menus in the _btnClick dialog event area. Heck in  
FBII/FB3 STD I handled popups in the doMouse area, so this isn't too  
strange.

Thanks again, and also for the other tips,

Paul