Do you use the designer, or do you code your gui manually?

[rajesh_clt3]

I created widget using designer and connection using manually.......

[GreyGeek]

Always the designer.

I also avoid using "clever code" which will give trouble to those that are going to be supporting my aps after June of next year. Writing "inspired" code which you can't figure out when you are not so "inspired" is foolish. The maintainers will hate you for it.

[alecs1]

Thank you for this discussion. Because of this I have finally took the time to learn using the forms, excelent.

[Colx007]

At the possible I use designer. But if I would know , I would use a text editor.

[C167]

I started with Qt4, and i started with the designer. I always had problems with the designer-generated UIs, i could not handle them. So i mainly use it now to visualize what i want to do and then hardcode it. One problem with generated widgets i had was that they never adjusted their size to the widget or mainwindow that contained them.

[jpn]

One problem with generated widgets i had was that they never adjusted their size to the widget or mainwindow that contained them.

It's a matter of installing a top-level layout on the form. Deselect child widgets and choose a layout from the Form-menu (or context menu or toolbar).

[MrShahi]

Not often, I use the designer when my gui design is very complex because it makes the gui very easily...........otherwise I prefer coding to design gui..................

[WinchellChung]

Newbie that I am, I generally use the Designer.

But occasionally when I am trying to add new items, it is a real pain to have to break all the layouts, or have Designer turn your dialog into a tangled mess.

In those cases I usually manually insert items into the *.ui file, using an XML editor.

[triperzonak]

i use designer almost everytime, but in my app i use designer in one form but in the other not..

and there is 1 proj that i cant use designer cause everything is dynamic..

in my kind of job where everything has deadline or timelimit or what ever you want to call that.. designer is very helpful..

[qwakaw]

I have always used designer to design the desired UI.. I really don't get the point why one should hardcode GUI.. In Qt 4, the stylesheets, promoting widgets etc gives you the power to achieve what you want with designer..

(OR)

I haven't come across the reqiurement wherby I need to do hardcoding GUI..

[ComaWhite]

I don't bother with signals/slots in them. Because the designer creates ugly naming of the slots. etc. But I use it everything else, but depending on what I need it for.

[rexi]

I mostly used the designer with KDevelop3. I'm still not exactly sure what is the right way to use it (or, the preferred way) I've been creating Qt apps with KDevelop, as well as with Eclipse. As I understand it, the first encourages subclassing, the latter encourages using the UI as a member. Now I'd like to know what most of the users of Qt prefer....

[lenardpi]

I use the designer for simple dialogs only.

The feature I would really need is being able to put a _subclassed_ widget onto the form. If there is already such a functionality, I don't know how to use it... What I can do is to use the Qt provided widgets only, but usually I'd like to work with eg. MyTabWidget instead of QTabWidget. I'd welcome Visual Studio's convenient solution in the designer for this issue.

[jpn]

The feature I would really need is being able to put a _subclassed_ widget onto the form. If there is already such a functionality, I don't know how to use it... What I can do is to use the Qt provided widgets only, but usually I'd like to work with eg. MyTabWidget instead of QTabWidget.

Yes, it's possible. See Promoting Widgets for more details.

[sneg]

I mostly use Designer for prototypes while I do the rest by hand.

[KaptainKarl]

I don't use QT Designer ever.
I guess I'm just old school and prefer controlling everything in my own code.
I also find QTs syntax for building layouts very intuitive so it's easy for me.

Karl

[ersin.ozkan]

%80 manually which is the best

[thiforums]

Honestly, dealing with layouts in qDesigner is bad and waste of time. If they add an anchors property for each visual control, it should become more easy, more comfortable and faster way to develop GUIs.

[rexi]

Honestly, NO! And it seems this is not only my opinion. Have a look at the other thread you started. Qt has one of the most advanced, flexible, easy to use layout systems I've ever seen. Sorry to say that, but anchors suck. You cannot design a good user interface with anchors

Qt's layouts are very simple. And that's what makes them very powerful. Just have a serious look at them, and I'm sure you will find out how you can achieve whatever you want it to be. With anchors, you just cannot...

Damn, in my opinion even Java's layouts are superiour to the anchor approach. And I really scorn most of Java's built-in layouts...

[ComaWhite]

Honestly, dealing with layouts in qDesigner is bad and waste of time. If they add an anchors property for each visual control, it should become more easy, more comfortable and faster way to develop GUIs.

What do you mean anchors?