Хм... попробуй всё снести и установить заново... я тоже качал от туда - проблем нет, может дело в твоём вижуале?

Редактирование форм лучше делать в Дизайнере, а не в студии.

Помощь лучше читать из Асистента, а не из студии.

Помощник для отладочной информации вписьІвается руками.

Правила moc, uic, rcc прекрастно вписьІваются руками, чем автоматически.

Что умеет дизайнер из того что не умеет интегратор?

Помощник для отладочной информации вписьІвается руками.
 А чё эта? ж))))

О ужас ! ж) Это конечно полезно уметь, да у меня всё руки не дойдут почитать как и разобраться раз и навсегда.

Здравствуйте, я тоже новичок в Qt.
У меня такая проблема: не могу понять как создавать свои собственные слоты. Если вмешаться в ui.h файл, то затем постоянно напоминает о том что он изменен, и это очень раздражает. Неужели нет штатного метода для этой цели, ведь в Qt3 Desiner все очень понятно.

2 Steven_Orko
Хочу поправить. СлотьІ могут возвращать значения и могут иметь аргументьІ по умолчанию. При етом коннектить к ним можно сигнальІ с произвольньІм колличеством параметром >= количеству параметров слота, которьІе не по умолчанию.

Slots
A slot is called when a signal connected to it is emitted. Slots are normal C++ functions and can be called normally; their only special feature is that signals can be connected to them. A slot's arguments cannot have default values, and, like signals, it is rarely wise to use your own custom types for slot arguments.
Since slots are normal member functions with just a little extra spice, they have access rights like ordinary member functions. A slot's access right determines who can connect to it:
A public slots section contains slots that anyone can connect signals to. This is very useful for component programming: you create objects that know nothing about each other, connect their signals and slots so that information is passed correctly, and, like a model railway, turn it on and leave it running.
A protected slots section contains slots that this class and its subclasses may connect signals to. This is intended for slots that are part of the class's implementation rather than its interface to the rest of the world.
A private slots section contains slots that only the class itself may connect signals to. This is intended for very tightly connected classes, where even subclasses aren't trusted to get the connections right.
You can also define slots to be virtual, which we have found quite useful in practice.
Compared to callbacks, signals and slots are slightly slower because of the increased flexibility they provide, although the difference for real applications is insignificant. In general, emitting a signal that is connected to some slots, is approximately ten times slower than calling the receivers directly, with non-virtual function calls. This is the overhead required to locate the connection object, to safely iterate over all connections (i.e. checking that subsequent receivers have not been destroyed during the emission), and to marshall any parameters in a generic fashion. While ten non-virtual function calls may sound like a lot, it's much less overhead than any new or delete operation, for example. As soon as you perform a string, vector or list operation that behind the scene requires new or delete, the signals and slots overhead is only responsible for a very small proportion of the complete function call costs.
The same is true whenever you do a system call in a slot; or indirectly call more than ten functions. On an i586-500, you can emit around 2,000,000 signals per second connected to one receiver, or around 1,200,000 per second connected to two receivers. The simplicity and flexibility of the signals and slots mechanism is well worth the overhead, which your users won't even notice.
Note that other libraries that define variables called signals or slots may cause compiler warnings and errors when compiled alongside a Qt-based application. To solve this problem, #undef the offending preprocessor symbol.