Cannot reach signals and slots editing mode.
A new-user problem: I cannot reach signals-and-slots editing mode.
I quote http://developer.qt.nokia.com/doc/qt-4.8/designer-connection-mode.html: "To begin connecting objects, enter the signals and slots editing mode by opening the Edit menu and selecting Edit Signals/Slots, or by pressing the F4 key."
Alas, I do not see "Edit Signals/Slots" in the Edit menu, nor does the F4 key do anything obvious besides putting this message on the bottom-left: "Click widgets to change the tab order..."
I am using Qt Designer 3.3.4 on i386 GNU/Linux.
welcome to devnet
Did you install Qt 4.8.0?
I am not familiar with Qt 3, but it looks that you are using the previous Qt version or at least the Qt designer of this version.
I didn't install anything. I'm not a sysadmin, but a mere user. Migrating to a more recent version is (apparently) a big deal--many users are involved other than me.
Qt Designer should display a more recent version. Than you will find the appropriate menu entry.
As I wrote already I am not familiar with Qt 3, but as it lookds you use a designer of Qt 3.
Qt 3 is not compatible with Qt 4. And for sure the documentation of 4.8.0 will not be compatible with Qt 3.
However, it does not make sense for you to start wth Qt 3, because this is outdated. My suggestion would be to get an administrator installing the most recent version, if possible.
Well, I work as sysadmin. Right now I'm a Fedora user but I've used all major Linux distributions, and so far all of them offer the latest version of software in their repositories, including Qt. In the case of Qt there is two branches, the 3.x and the 4.x. I believe they keep the 3.x branch just for compatibility reasons, so the fact that 4.x is the new stable version it's enough for me. Not to mention obvious things like new features and improvements introduced with the 4.x branch, so as koahnig said now days doesn't make any sense starting with Qt 3. From my point of view upgrading to the 4.x branch and migrating your projects it's a step forward that you and the other users involved will appreciate, for the reasons commented above and definitely others that you will discover. So if your sysadmin does what needs to be done and isn't a lazy one, he/she should understand without creating a big issue for you.