<title>Creating dialog boxes in &kappname;</title>
<para/>
<para>This section is a developer's guide explaining the peculiarities of dialog creation in &kappname;. A basic understanding of Qt GUI programming is assumed, as is a knowledge of &kappname; coding standards as laid out in the Project Handbook.</para>
<para>This section is a developer's guide explaining the peculiarities of dialog creation in &kappname;. A basic understanding of TQt GUI programming is assumed, as is a knowledge of &kappname; coding standards as laid out in the Project Handbook.</para>
<para/>
<sect1 id="dialogs-language">
<title>Language</title>
@ -18,7 +18,7 @@
<sect1 id="dialogs-designing">
<title>Designing the dialog</title>
<para/>
<para>The dialog screen should be built using Qt Designer. This section assumes that you are using version 3.x of Qt. Version 4 is, at present, an unknown quantity.</para>
<para>The dialog screen should be built using TQt Designer. This section assumes that you are using version 3.x of TQt. Version 4 is, at present, an unknown quantity.</para>
<para/>
<para>Open Designer without specifying a project, and select Dialog from the New File/Project tab. Start by changing the form name; this should be set to '<KN>DlgDecl'.</para>
<para/>
@ -35,7 +35,7 @@
<para/>
<para>Designer contains an option to generate shortcut (accelerator) keys for various widgets (buttons, menu items) by including an ampersand ('&') before the shortcut letter. This should be used for the more common items, since many users prefer to use keyboard input rather than using the mouse. However, this does have the unfortunate side effect of automatically generating an 'accel' property for the widget, referencing a letter which may not be appropriate when the caption is translated to another language. Use the properties menu, therefore, to remove this value, or see below.</para>
<para/>
<para>Fixed text fields and labels in the form do not require any special consideration. Qt Designer and the project's build environment will take care of wrapping the strings into an i18n construct for presentation to translators.</para>
<para>Fixed text fields and labels in the form do not require any special consideration. TQt Designer and the project's build environment will take care of wrapping the strings into an i18n construct for presentation to translators.</para>
<para/>
</sect2>
<sect2 id="dialogs-saving-ui">
@ -72,9 +72,9 @@
<para/>
<para>The first two lines are the standard include stoppers, to avoid multiple inclusion of the class data.</para>
<para/>
<para>The include file will have been generated by the Qt UIC (User Interface Compiler) from the .ui file for the dialog, under control of the make process.</para>
<para>The include file will have been generated by the TQt UIC (User Interface Compiler) from the .ui file for the dialog, under control of the make process.</para>
<para/>
<para>The TQ_OBJECT macro (written without any punctuation) will cause the Qt MOC (Meta Object Compiler) to generate additional object code and files which are necessary to support the signal/slot functionality (among other things).</para>
<para>The TQ_OBJECT macro (written without any punctuation) will cause the TQt MOC (Meta Object Compiler) to generate additional object code and files which are necessary to support the signal/slot functionality (among other things).</para>
<para/>
<para>The class declaration must also include a </para>
<para/>
@ -85,7 +85,7 @@
<programlisting> signals:</programlisting>
<para/>
<para>sections if you plan to use the signal/slot mechanism. See the Qt documentation about signals and slots. An example would be slotHelp() which will be connected to the clicked() signal of the help button of your dialog in the constructor of your dialog.</para>
<para>sections if you plan to use the signal/slot mechanism. See the TQt documentation about signals and slots. An example would be slotHelp() which will be connected to the clicked() signal of the help button of your dialog in the constructor of your dialog.</para>
<para/>
<para>Terminate the file with</para>
<para/>
@ -97,9 +97,9 @@
<sect2 id="dialogs=code-file">
<title>Code (.cpp) file</title>
<para/>
<para>First, don't forget to have #include directives for Qt headers for any widgets you are going to reference.</para>
<para>First, don't forget to have #include directives for TQt headers for any widgets you are going to reference.</para>
<para/>
<para>In the constructor function, connect all signals to their appropriate slots using the Qt connect() call.</para>
<para>In the constructor function, connect all signals to their appropriate slots using the TQt connect() call.</para>
<para>This is one of the files generated by the Qt MOC (Meta Object Compiler) during the make process; if you finish up with 'vtable' errors, it's probably because you forgot to include this.</para>
<para>This is one of the files generated by the TQt MOC (Meta Object Compiler) during the make process; if you finish up with 'vtable' errors, it's probably because you forgot to include this.</para>
