Originally posted by scooter
(Newbie using Qt 3.2 under Linux)
- A file with the extensions '.cqt', or '.hqt' resp., added to a project list will be not shown in this list. You are forced to use '.c'/'.cpp', or '.h'/'.hpp' resp., to get it visible.
In general its better if you use .cpp/.hpp , it gives make a hint as to what compiler to use (gcc or g++). if its '.cqt' - what is it supposed to use? While you are still a newbie, respect these sorts of standards. It will be easier for you.
- Quite often the layout of my widgets is shifted and/or have other sizes, although I didn't touch it. It costs a lot of time to reorder the layout. The provided layout manager is no help.
The widgets are supposed to resize when the entire dialog/window resizes. Thats the whole point. Unlike VB6 where the widgets stay exactly where they are put, but you then have to write the code to resize all the widgets correctly.
You can make them static, by not using any layouts at all. You can set the size policies to Fixed, and set the sizes in designer.
- By the way, the layout manager: You will get shortened dialog boxes when you compile your codes with the red lines of the layout manager not removed from your dialogs - the lower half of all widgets at the dialog bottom is missing. There is no hint in the manual. I found a solution by chance.
And, it looks like the rest of us will have to also find the solution by chance - unless you tell us what it is !

whats the point of complaining about some random "bug" if you dont even tell us the whole story.
- Very often I'm not able to use the Ctrl-T accelerator to display a dialog preview. I have to use the menu item instead.
If your other menu items work (like ctrl-q for quit), then its likely to be your Window Manager's fault that ctrl-T doesn't work. In that case, QT has absolutely NOTHING to do with this problem, and should not have been blamed.
- I found no dialog property to force the dialog to be displayed monitor-centered (or other) when shown. The mainform dialog jumps widely over the screen at each program launch, depending on the other task's dialogs positions. MS Windows does better here...
Again, you anger me by jumping to the conclusion that "Since I can't do it, therefore it can't be done, therefore MS Windows is better". That does reflect how much of a newbie you are and how much you have to learn. Don't mistake your ignorance for a bug.
Try looking at the QSplashScreen code, that puts the dialog in the middle of the screen every time.
- I found no way to fix a widget's size to a certain value with no chance of the layout manager to change it...
Try setting the size-policies to Fixed
- The 'frameShape' and 'frameShadow' properties of some widgets offer items which have no changing effect on the widget: The previous frame style remains. Changing to another style and changing back to the first style (i.e., not this style is the current frame property item) has no effect to the widget: it keeps the style it had before the last change.
Not sure here, but I would guess that some widgets don't use the frame-shape/shadow property. Maybe their frames are hidden? I dunno.
- QTable: I have a spreadsheet with two columns, both with strings written into them. The first is a QString containing digits. Contrary to documentation, this QString is not aligned to the left but to the right as if it was an integer.

The other string, a const char[], is aligned correctly. Who can help?
Does the other string also contain integers? You might find that (like spreadsheets like lotus-123, excel and probably OO calc), ANY string that is a number is aligned to the right. Its well known that numbers are better aligned to the right in such situations like accounting (where spreadsheets are used the most).
If you want to change that, then you need to specify the alignment. I dunno how, but there is a way, even if you have to reimplement ::paintEvent()
- Diabling a menu item (which has sub-items) while designing greys this item and its sub-items. When checking the preview, only the sub-items are greyed.
Did you check the compiled result? Sometimes the designer doesn't reflect what truely happens, and sometimes the preview doesn't reflect what happens. Its only the resulting code that is important. Whatever the code does, is supposed to happen. Everything else is an approximation.
Well, that's it for now...

)
I'm glad. Try not to make judgements until you know all the facts, it only displays your ignorance of your ignorance. Having said that, I hope I haven't displayed mine.
Debboy.