cc (ddlmZdZGddZy))Gtkz*/com/github/maoschanz/drawing/optionsbars/cdeZdZdZdZdZdZdZdZdZ dZ dZ d Z d Z d Zd Zd ZdZy)AbstractOptionsBarc d|_d|_y)NiF) _limit_size _is_narrowselfs =/usr/lib/python3/dist-packages/drawing/abstract_optionsbar.py__init__zAbstractOptionsBar.__init__s$$/c|tjjt|z}|j d|_|j d|_|j d|_|j d|_|j d|_ |j d|_ |j|_ |S)aLCreates a Gtk.Builder for the resource whose path is hinted in the method parameter, and tries to extract usual widgets ids from it. Most resulting widgets can be `None`, except `action_bar`. The builder is returned if the caller wants to extract more objects from it. This is valid for any instance of `AbstractOptionsBar`.z bottom-pane cancel_btn centered_box apply_btnhelp_btn options_btn) rBuildernew_from_resource RSRC_PREFIX get_object action_barrrrrr_togglable_btn)r end_of_pathbuilders r _build_uizAbstractOptionsBar._build_uis KK ) )+ *C D'&&}5$/&&|4$/((8$%%k2$.$$Z0$-'' 6$(($ .r cjtjjt|z}|j d|_|j j|j |j d}|r|jj||S|jjd|_|S)aSame as above, BUT this isn't valid for any instance of `AbstractOptionsBar`: only an optionsbar for a transform tool should call that method, and it should call it *after* `_build_ui`. This method will "hydrate" the previously built (but still incomplete) widgets.rz actions-menuN) rrrrrrrset_center_widgetrset_menu_modeldestroy)r rr actions_menus r _hydrate_transform_toolz*AbstractOptionsBar._hydrate_transform_tool.s KK ) )+ *C D'((8$//##D$5$56##N3,""<0 .4 .r cy)zSet a widget (or a menu) as the popover with tools options. In practice this is used only with the classic tools' pane, and all classic tools provide a menu instead of a widget.N)r widgetmodellabels r build_options_menuz%AbstractOptionsBar.build_options_menu>r cy)zUpdate the pane when a tool using it has just been activated. Widgets may be hidden/shown or enabled/disabled depending on the properties of the given tool.Nr$)r tools r update_for_new_toolz&AbstractOptionsBar.update_for_new_toolDr)r cyNr$r s r get_minimap_btnz"AbstractOptionsBar.get_minimap_btnJr cyr.r$)r r's r set_minimap_labelz$AbstractOptionsBar.set_minimap_labelMr0r c|jrP|jjr5|jj|jj yyyr.)r get_visible set_active get_activer s r toggle_options_menuz&AbstractOptionsBar.toggle_options_menuPsJ T00<<>!!d&9&9&D&D&F"FG?r cT|jr|jjdyy)NF)rr5r s r hide_options_menuz$AbstractOptionsBar.hide_options_menuTs$ !!%(r cyr.r$r s r middle_click_actionz&AbstractOptionsBar.middle_click_actionXr0r cZ|jd|jjy)aEInstructions to run during the first window size allocation (and only the first). Calling this is managed by the window's `DrOptionsManager`. It estimates the minimal amount of pixels for the mobile version, and gives it to the `_set_limit_size` method. Any implementation HAS TO end with a call to `_set_limit_size`!FN) set_compactrshow_allr s r init_adaptabilityz$AbstractOptionsBar.init_adaptability[s" 5//r cLtd|z|_|jdy)Ng?T)intrr=)r temp_limit_sizes r _set_limit_sizez"AbstractOptionsBar._set_limit_sizees"/0$4r c~||jkD}||jk(}|r|j|j yy)zCheck whether or not the costly `set_compact` method should be called, depending on a given window width, and the pane's limit previously set.N)rrr=)r allocated_width can_expand incoherents r adapt_to_window_sizez'AbstractOptionsBar.adapt_to_window_sizeis? $"2"22*doo-*'(r cd||_|j|jj| yy)zUThe parameter is a boolean telling if the bottom pane should become compact or not.N)rr set_visible)r states r r=zAbstractOptionsBar.set_compactrs.$/ ]]==Y'r N)__name__ __module__ __qualname____gtype_name__r rr"r(r,r/r2r7r9r;r?rCrHr=r$r r rrsN&     H))(r rN) gi.repositoryrrrr$r r rQs$: a(a(r