<para>! WARNING ! THE LABELS OF THE PREVIOUS FOUR BUTTONS MUST ONLY BE DEFINED ONCE IN THE PROGRAMME (HERE), AND ONLY USING THE FOUR FOLLOWING FUNCTIONS: </para>
<para>! WARNING ! THE LABELS OF THE PREVIOUS FOUR BUTTONS MUST ONLY BE DEFINED ONCE IN THE PROGRAMME (HERE), AND ONLY USING THE FOUR FOLLOWING FUNCTIONS: </para>
<para>The rules page consists of two half-pages in a GtkPaned widget : </para>
</para>
<para><itemizedlist>
<listitem>
<para>on the left, widgets for controlling or editing all the rules.</para>
</listitem><listitem>
<para>on the right, widgets for controlling or editing the selected rule.</para>
</listitem></itemizedlist>
</para>
<para>As this division is clear and constant, it is simpler to place these two half-pages at the same hierarchical level as the other full pages like "synth", "state" or "results".</para>
<para>So there is no: "widget_get_rules_page()" function. Instead, the distribution: "all rules" versus "the selected one" is moved to the file: "signal".</para>
<para>It is in the function: static void switch_state_rules_data() { switch (<linklinkend="_fsm_8h_1a90ab14081a88752d3721947a4922ee25">fsm_get_state_rules_data()</link>) { ... case (RULES) : GtkPaned *widget_all_vs_selected_one = ... break; ... }</para>