Tk Source Code

 *    Ttk expects the up and down arrows to be distinct elements but HIToolbox
 *    draws them as one widget with two different pressed states.  We work
 *    around this by defining them as separate elements in the layout, but
 *    making each one have a drawing method which also draws the other one.
 *    The down button does no drawing when not pressed, and when pressed draws
 *    the entire IncDecButton in its "pressed down" state.  The up button draws
 *    the entire IncDecButton when not pressed and when pressed draws the
 *    IncDecButton in its "pressed up" state.




 */

static Ttk_Padding SpinbuttonMargins = {0, 0, 2, 0};
static void SpinButtonUpElementSize(
    void *clientData, void *elementRecord, Tk_Window tkwin,
    int *minWidth, int *minHeight, Ttk_Padding *paddingPtr)
{

 *    Ttk expects the up and down arrows to be distinct elements but HIToolbox
 *    draws them as one widget with two different pressed states.  We work
 *    around this by defining them as separate elements in the layout, but
 *    making each one have a drawing method which also draws the other one.
 *    The down button does no drawing when not pressed, and when pressed draws
 *    the entire IncDecButton in its "pressed down" state.  The up button draws
 *    the entire IncDecButton when not pressed and when pressed draws the
 *    IncDecButton in its "pressed up" state.  NOTE: This means that when the
 *    down button is pressed the IncDecButton will be drawn twice, first
 *    in unpressed state by the up arrow and then in "pressed down" state by
 *    the down button.  The drawing must be done in that order.  So the up
 *    button must be listed first in the layout.
 */

static Ttk_Padding SpinbuttonMargins = {0, 0, 2, 0};
static void SpinButtonUpElementSize(
    void *clientData, void *elementRecord, Tk_Window tkwin,
    int *minWidth, int *minHeight, Ttk_Padding *paddingPtr)
{