eve_client_holder Struct Reference

#include <factory.hpp>

List of all members.

Public Member Functions
	eve_client_holder (behavior_t &sheet_scope_root_behavior)
	~eve_client_holder ()
Public Attributes
assemblage_t	assemblage_m
dictionary_t	contributing_m
behavior_t::verb_token_t	eve_eval_token_m
eve_t	eve_m
sheet_t	layout_sheet_m
behavior_t *	my_behavior_m
boost::filesystem::path	path_m
behavior_t &	root_behavior_m
platform_display_type	root_display_m
boost::signal< void()>	show_window_m
visible_change_queue_t	visible_change_queue_m

---

Detailed Description

Definition at line 62 of file factory.hpp.

---

Constructor & Destructor Documentation

eve_client_holder

(

behavior_t &

sheet_scope_root_behavior )

Definition at line 64 of file factory.hpp.

~eve_client_holder

(

)

Definition at line 74 of file factory.hpp.

---

Member Data Documentation

assemblage_t assemblage_m

This is the assemblage which widget factories register the created widget (or wrapping structure) with, such that the widget gets deleted when the assemblage does.

Definition at line 103 of file factory.hpp.

dictionary_t contributing_m

A set for the contributing factors to the sheet (not the layout sheet)

Definition at line 108 of file factory.hpp.

behavior_t::verb_token_t eve_eval_token_m

Used by the eve_client_holder to disconnect itself from the root behavior.

Definition at line 140 of file factory.hpp.

eve_t eve_m

The Eve engine which all of these widgets are being inserted into. This must be known by top-level windows, and by widgets which manage trees of Eve widgets (such as splitter widgets).

Definition at line 91 of file factory.hpp.

sheet_t layout_sheet_m

The layout sheet is sheet used to hold the layout state.

Definition at line 96 of file factory.hpp.

behavior_t* my_behavior_m

REVISIT (sparent) : We really need a generalized mechanism for deferring an action - a command queue of sorts - which collapses so things don't get done twice. We hack it here.

Definition at line 146 of file factory.hpp.

boost::filesystem::path path_m

Path to the file loaded for this window.

Definition at line 156 of file factory.hpp.

behavior_t& root_behavior_m

Relayout is complicated. We need to maintain a visible update queue (VUQ) per-window, as we want to know when a window has hide/show elements in their respective queues; this helps to eliminate unnecessary calls to eve_t::evaluate for a given window if none is needed. However, we also need to call _all_ the VUQ update routines related to a given sheet- this is needed to make sure all the views are updated w.r.t. the state of the sheet so there are no hide/show sync issues. This reference is held to the 'root behavior', the one scoped the same as the sheet to which this view will be bound, and the behavior called when a user action requires us to check the VUQ set for the sheet for potential relayout.

Definition at line 135 of file factory.hpp.

platform_display_type root_display_m

Display token for the root item in the view.

Definition at line 151 of file factory.hpp.

boost::signal<void ()> show_window_m

Top-level widgets (windows, dialogs, etc) need to be told to show themselves when all of the child widgets have been created and inserted. This signal is issued when the top-level window needs to be shown -- so any factory function which creates a window needs to connect to this signal.

Definition at line 116 of file factory.hpp.

visible_change_queue_t visible_change_queue_m

REVISIT (sparent) : We really need a generalized mechanism for deferring an action - a command queue of sorts - which collapses so things don't get done twice. We hack it here.

Definition at line 122 of file factory.hpp.