I have changed the .h file 'linked' to the .ui file
(because I have deleted the statusbar and now I want it again)
1.- Is there a way to say QTcreator 'rebuild .ui from .h ?'
2.- Is there a way to add a statusbar in QTCreator?
I have changed the .h file 'linked' to the .ui file
(because I have deleted the statusbar and now I want it again)
1.- Is there a way to say QTcreator 'rebuild .ui from .h ?'
2.- Is there a way to add a statusbar in QTCreator?
Not that I'm aware of. Did you delete the status bar using the designer?
QMainWindow has one by default. You can just use that one. Else call statusBar() in your code.
Revision control for the win
Horse sense is the thing that keeps horses from betting on people. --W.C. Fields
Ask Smart Questions
Yes, I delete it from designer.
And, I want to use it at the designer, not in code.
Open the .h file generated from the ui file, scroll to the top and read the line containing the word "WARNING" as many times as you need until you understand it. Then go to the documentation and read the Using a Designer UI File in Your Application chapter. Pay special attention to sentences containing the word "subclass".
Wysota, I know to read...
This is the reason to make this 2 questions.
1.- Is there a way to say QTcreator 'rebuild .ui from .h ?'
2.- Is there a way to add a statusbar in QTCreator?
It can be interesting to say QT People that include this functionality in next versions.
For example, in this way a copy - paste operations could allow to build a menu from code. (for example). But I understand that it can be very difficult.
Last edited by tonnot; 24th November 2010 at 10:12.
No, it wont be interesting for them.It can be interesting to say QT People that include this functionality in next versions.
For example, in this way a copy - paste operations could allow to build a menu from code. (for example). But I understand that it can be very difficult.
The designer is a help tool to help rapid ui design.
The ui file is just a way to convey that information to your C++ code.
ui's do not have any importance on their own.
If you changed something in your code that changes the way your GUI looks like, then there is no need to change the ui back form the code, since your code is your application and it does what you want.
Many people don't bother with ui's at all, but code everything manually.
==========================signature=============== ==================
S.O.L.I.D principles (use them!):
https://en.wikipedia.org/wiki/SOLID_...iented_design)
Do you write clean code? - if you are TDD'ing then maybe, if not, your not writing clean code.
Yes, but If they want to have a century XXI's tool and win users, later or sooner they have to integrate code with UI in biunivocal way.
ok, you win.
==========================signature=============== ==================
S.O.L.I.D principles (use them!):
https://en.wikipedia.org/wiki/SOLID_...iented_design)
Do you write clean code? - if you are TDD'ing then maybe, if not, your not writing clean code.
Yes, right click the form and choose "Add status bar". Not that you'll be able to do anything with the status bar from within Designer apart setting its properties...
I don't think there are tools for painters to decompose paintings into blobs of paint and stuff that paint back into tubes.It can be interesting to say QT People that include this functionality in next versions.
For example, in this way a copy - paste operations could allow to build a menu from code. (for example). But I understand that it can be very difficult.
It's written numerous times in numerous places - never modify files that are generated on the fly (ever, not only in Qt). You are given mechanisms for modifying the looks and behaviour of UIs generated from .ui files in your code so use them. If you stride sideways and go your own way then you will be on your own. Deal with it.
Bookmarks