$(QTNATIVELIBS) -lbqplot_native -lbanner -lbrttutil -lbumapdata $(DBLIBS) $(TRLIBS) #include "BQ.h"
This class inherits the BQConfigure class which is itself a subclass of the BUConfigure class with extensions to process Qt colors and fonts. The configure methods are implemented in the BUConfigure parent (see BUConfigure(3)).
BQTaskbar(BQViewport *master);
Where "master" is the BQViewport master for this object.
buttons_definitions &Arr{ basemap &Arr{ height 26 description base map states &Arr{ bluemarble &Arr{ label B description NASA Bluemarble action configure maplayers_template bluemarble opacity 0.5 background_color blue fill_color yellow order 0 } vector &Arr{ label V description vector shorelines action configure maplayers_template vector opacity 0.5 background_color #fff2e5 fill_color black order 1 } } } zoomin &Arr{ height 26 label + description zoom in opacity 0.5 background_color white fill_color black bpq_layer vector action &Tbl{ mod=shift configure zoom 2.0 mod=notshift configure zoom 1.1 } } zoomout &Arr{ height 26 label - description zoom out opacity 0.5 background_color white fill_color black bpq_layer vector action &Tbl{ mod=shift configure zoom 0.5 mod=notshift configure zoom 0.9090909090909 } } } /B>
- states
If this exists and is an associative array, then it defines a set of button states that all will occupy the same button position in the taskbar. Each entry in the states array must also be associative arrays that define the parameters for each button state. When multiple states are defined, then a left mouse click on the button will cycle through the states. The label, description, action, opacity, background_color and fill_color parameters for each button state are defined below. In addition, the order parameter defines the order of the buttons as they are cycled. Note that when states is specified, then the label, description, action, opacity, background_color and fill_color parameters must be in each button state array.- description
This is a description string that is displayed as a tool tip using a BQTextPopup object. You can define descriptions for each button state as well as for a button ityself when there are multiple states.- label
This is a text label that will be displayed in the button.- opacity
This is a floating point opacity value that is applied to the button rendering relative to the layers underneath it. A value of 1.0 means complete opaque and a value of 0.0 means completely translucent.- background_color
This is the button background color. If this is "", then the background is not filled. If this is "$BACKGROUND", then the default value corresponding to option taskbar_background will be used. Can be specified in any of the forms documented in BQ_ParseColor(3).- fill_color
This is the button text fill color. If this is "", then the text label is not displayed. Can be specified in any of the forms documented in BQ_ParseColor(3).- action
This is a string that defines the action that will be taken when the button is pressed. This can either be a table of actions, in which case each action in the table is performed in the order in which it appears, or a single action. The following whitespace separated fields define the action to be taken. The first field is the action type and currently can only be configure, which means to run the configure method. The following two fields are used to define the configure option name and the option value. An optional mouse modifier field can precede the type field. This optional modifier field should always start with mod=. The string after the mod= prefix defines mouse modifiers that must be present in order for that action to be taken. Currently the only modifiers defined are shift, meaning that the SHIFT key was pressed when the mouse button was pressed, or notshift, meaning the SHIFT key was not pressed when the mouse button was pressed. This provides a means for changing the action parameters based upon modifier keys. Note that typically a BQTaskbar object is created by another object, for example a BQMap object. The object that creates the BQTaskbar object will usually arrange for the BQTaskbar object to properly process the calling object's configuration parameters through a call to BUConfigure::setConfigureSpecs (see BUConfigure(3)) using the calling object's parameter structure.
buttons &Tbl{ basemap neb 1.0v-10 1.0v-10 1 zoomin neb -1r 0r zoomout neb -1r 0r }