Lines Matching refs:p

53     <p>There are two configurations of resources:<ul>
60     </ul></p>
62     <p>When the two configurations differ then the current configuration is
71     </ol></p>
73     <p>Requests for configuration changes are handled in a two step process:
89     views in the side panes.</p>
90     <p>This process goes on until the queue of request objects becomes
92     modified.  No resources have been activated or deactivated.</p></li>
94     <li><p>The second update step activates or deactivates resources so that
96     resources) reflects the requested configuration.</p>
97     <p>The order in which resources are activated or deactivated depends on
101     unrelated resources.</p>
102     <p>Note that the second update step may not be able to activate (or even to
110     requested once more.</li></ol></p>
112     <p>The configuration controller sends the following events:
118     <member>requestResourceActivation()</member> call is made.</p>
119 … <p>The <member scope="ConfigurationChangeEvent">ResourceId</member> member is set to the requested
121     set.</p></li>
126     example <member>requestResourceDeactivation()</member> is called.</p>
127     <p>The <member>ResourceId</member> member is set to the requested
129     set.</p></li>
131     the current configuration starts.</p>
132     <p>The requested configuration is available in the <member
135     are not set.</p></li>
137     the current configuration ends.</p>
138     <p>The requested configuration is
141     <member>ResourceObject</member> members are not set.</p></li>
144     from a cash).</p>
145     <p>The <member>ResourceId</member> and <member>ResourceObject</member>
147     the activated resource.</p></li>
150     configuration is removed from the configuration.</p>
151     <p>The <member>ResourceId</member> and <member>ResourceObject</member>
153     deactivated resource.</p></li>
154     </ul></p>
163         <p>The request is processed asynchronously.  Notifications about
164         configuration changes are sent after this call returns.</p>
168             <p>When eMode is <const>REPLACE</const> then, before adding the
173             activating a new view the old one has to be deactivated.</p>
174             <p>When eMode is <const>ADD</const> then the resource is requested
175             without further changes.</p>
182         <p>The request is processed asynchronously.  Notifications about
183         configuration changes are sent after this call returns.</p>
184         <p>Requesting the deactivation
185         of a resource that is not active is not an error.</p>
206         <p>This is only necessary when more than one change request is being
208         changes) before all change requests are being made.</p>
209         <p>Recursive <member>lock()</member> calls are recognized: the
211         called more often than <member>unlock()</member>.</p>
216         <p>When <member>unlock()</member> is called as many times as
220         configuration will eventually being made.</p>
225         <p>Call it when a resource is activated or deactivated
228         be necessary.</p>
233         <p>Modifications to the returned configuration have no effect on the
234         drawing framework.</p>
239         <p>Modifications to the returned configuration have no effect on the
240         drawing framework.</p>
246         <p>Together with the <member>getCurrentConfiguration()</member> and
249         given configuration can have other origins then these methods.</p>
250         <p>The given configuration is transformed into a list of of change
254         changes are properly broadcasted.</p>
255         <p>Note that because of the configuration change notifications
258         configuration.</p>