![]() Maybe I'm wrong, I'm still consider the design concept, but before we get to the answer, I need everyone think of this question.Īs for me, I prefer old Qucs interface with Tabs (firefox-like). ![]() I suggest that, though someone may dislike this, in the future, one file per window will be necessary, this eliminate the needs of becomeCurrent and makes the function of each window more clearly. I'm not sure how others think, but I feels that putting every file into same window will limit the progress of adding new function. The implementation of becomeCurrent will quickly become unmanageable. Insert menu in schematic and layout will definitely have different contents. Also, each type of document uses different QActions. In current state, there are only two doc, if we wanna add another file type, we may have to change becomeCurrent in each files. There are more function handle what to do when user switch to other tab, in every case, determining the file type, casting the pointer are also required. If we add Layout Document, EM simulation document, the function like getDoc will become crazy. Since what QTabWidget stores is QWidget, not QucsDoc, and QWidget doesn't have the function interface needed, we need first change it into QucsDoc. This design use single window to manage all design files, but it also shows many drawback. In mainwindow, all open files will add into tabwidget in mainwindow, and all files share same window menu. Both files are double inherited from Qwidget and QucsDoc, with QucsDoc provides some function interface like becomeCurrent, DocName. Here is the issue need to be discussed.Ĭurrently qucs support two type of doc: schematic, and pure text document textdoc. ![]() Recently I spend some time so watch and clean up code in qucs.cpp, the main program. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |