As stated in the topic, I remember h file usually written in c + + programming statements, CPP file write implementation, written in Qt Creater generates a what also have no program, open the looked at the mention of this header file, found it necessarily has achieved,
CodePudding user response:
CodePudding user response:
This file is intermediate files generated by the compiler for the UI, UI file in XML format, Qt at compile time, use of uic tool first mainwindow. UI compiled ui_mainwindow. H, converted to c + + class, is the UI: : mainwindow, then in the mainwindow. One of the CPP UI member variable is initialized to UI: : mainwindow, achieve the goal that can access interface in your application,
CodePudding user response:
The CPP don't need you to change
CodePudding user response:
Why in the h file "implementation", language thing, don't be too serious
CodePudding user response:
The
reference 3 floor walk every step response: the CPP don't need you to change I do not want to change this stuff, I just want to ask, don't I said beautiful a woman is going to marry her to do the wife? Ha ha, CodePudding user response:
The reference 4 floor walk every step response: why there are "implementation", in the h file language thing, don't too truer Only you is the topic the most accurate, recently met a lot of answers to questions alone is said is right, but don't match and problem, but still thank you for your enthusiastic, CodePudding user response:
refer to the second floor hzh_Beyond response: this file is intermediate files generated by the compiler for the UI, UI file in XML format, Qt at compile time, use of uic tool first mainwindow. UI compiled ui_mainwindow. H, converted to c + + class, is the UI: : mainwindow, then in the mainwindow. One of the CPP UI member variable is initialized to UI: : mainwindow, achieve the goal that can access interface in your application, You said is right, thanks for patience to answer, but I really want to know is as a h file, why has the function of the realization of, should not only statement, and then in the CPP implementation? I think is because the single Ui_MainWindow class is relatively simple, so the Qt so dry? I am not pick on Qt, Qt is great in my heart, CodePudding user response:
reference 7 floor for me - also division also friends your replies: Quote: refer to the second floor hzh_Beyond response: This file is intermediate files generated by the compiler for the UI, UI file in XML format, Qt at compile time, use of uic tool first mainwindow. UI compiled ui_mainwindow. H, converted to c + + class, is the UI: : mainwindow, then in the mainwindow. One of the CPP UI member variable is initialized to UI: : mainwindow, achieve the goal that can access interface in your application, You said is right, thanks for patience to answer, but I really want to know is as a h file, why has the function of the realization of, should not only statement, and then in the CPP implementation? I think is because the single Ui_MainWindow class is relatively simple, so the Qt so dry? I am not pick on Qt, Qt is very great, in my heart Classmate, you learn more language would not have this kind of question, Java is a file, And the benefits of separate files and CPP, you need to know about the process, the program compiled Header files include were cultured in large projects, huge amounts of code, You can't imagine office source all compile a need for a few days? CodePudding user response:
QT source has a lot to learn, there are a lot of convenient software engineering knowledge and truth, Don't know how much better than the design of the MFC CodePudding user response:
reference 7 floor for me - also division also friends your replies: Quote: refer to the second floor hzh_Beyond response: This file is intermediate files generated by the compiler for the UI, UI file in XML format, Qt at compile time, use of uic tool first mainwindow. UI compiled ui_mainwindow. H, converted to c + + class, is the UI: : mainwindow, then in the mainwindow. One of the CPP UI member variable is initialized to UI: : mainwindow, achieve the goal that can access interface in your application, You said is right, thanks for patience to answer, but I really want to know is as a h file, why has the function of the realization of, should not only statement, and then in the CPP implementation? I think is because the single Ui_MainWindow class is relatively simple, so the Qt so dry? I am not pick on Qt, Qt is very great, in my heart Speak really, have never thought you will be entangled with this point, CodePudding user response:
refer to walk every step of the eighth floor response: Quote: refer to 7th floor for me -- you also division also friend replies: Quote: refer to the second floor hzh_Beyond response: This file is intermediate files generated by the compiler for the UI, UI file in XML format, Qt at compile time, use of uic tool first mainwindow. UI compiled ui_mainwindow. H, converted to c + + class, is the UI: : mainwindow, then in the mainwindow. One of the CPP UI member variable is initialized to UI: : mainwindow, achieve the goal that can access interface in your application, You said is right, thanks for patience to answer, but I really want to know is as a h file, why has the function of the realization of, should not only statement, and then in the CPP implementation? I think is because the single Ui_MainWindow class is relatively simple, so the Qt so dry? I am not pick on Qt, Qt is very great, in my heart Classmate, you learn more language would not have this kind of question, Java is a file, And the benefits of separate files and CPP, you need to know about the process, the program compiled Header files include were cultured in large projects, huge amounts of code, You can't imagine office source all compile a need for a few days? A great god, I just want to ask this file, as a. H file, why there are implemented? . H. The advantages of CPP apart I know ah, I am not asking this, you said what other similar to Java, and Office source code or something I don't know, I don't think you to the great god despise me, didn't answer my questions well, ha ha, CodePudding user response:
references to the tenth floor hzh_Beyond response: Quote: refer to 7th floor for me -- you also division also friend replies: Quote: refer to the second floor hzh_Beyond response: This file is intermediate files generated by the compiler for the UI, UI file in XML format, Qt at compile time, use of uic tool first mainwindow. UI compiled ui_mainwindow. H, converted to c + + class, is the UI: : mainwindow, then in the mainwindow. One of the CPP UI member variable is initialized to UI: : mainwindow, achieve the goal that can access interface in your application, You said is right, thanks for patience to answer, but I really want to know is as a h file, why has the function of the realization of, should not only statement, and then in the CPP implementation? I think is because the single Ui_MainWindow class is relatively simple, so the Qt so dry? I am not pick on Qt, Qt is very great, in my heart Speak really, have never thought you will be entangled with this point, Yes, a little entanglements ah, since the ask, see what the great god, but they are universally felt great god I ask don't look good, a little said I "don't ask anyone ask ghosts and gods", CodePudding user response:
references 9/f, walk every step response: there is a lot to learn in QT source, there are a lot of convenient software engineering knowledge and truth, Better than the design of the MFC don't know how many MFC contact, I am at a loss, in the end, into the. Net, delicious! Want to study Qt. CodePudding user response:
1. Ui_xxx. H is qmake according to XXX. The UI files automatically generate a header file 2. Qt this design pattern is a classic design patterns, you can be thought of as a build mode plus decorator pattern, Qt source is a treasure to c + +, there is a lot of lessons if you often go to the place, if you want to do complicated desktop app Suggestions can read QtCreator source nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull