sedi (19th July 2013)
That is not so easy or the most usefull way to do it.
Writing a plugin isn't so easy and there is the problem of different compilers platforms.
I don't understand what it means :
-----
Promoting a widget doesn't yield any benefits other than forcing uic to generate code for the promoted widget instead of its superclass. Bearing the fact that uic doesn't create the top-most widget, promoting it doesn't make any sense, the code generated by uic would be identical with the only exception that setupUi() would have a different argument type which would give no additional value considering the presence of inheritance in C++ where you can pass a subclass to a function that expects a superclass.
----
Look at what I expect:
Last edited by mingodad; 16th April 2010 at 12:34.
FormBase is derived from QWidget so you don't need to promote the form to FormBase, it can be QWidget-based without losing any functionality.
Promoting the layout doesn't make much sense as you wouldn't be able to use the added functionality in Designer anyway so it's easier to leave blank space on the form and then place the new layout in code. Otherwise you will have WYSINWYG (what you see is not what you get) semantics. You have to accept the fact you can't do everything with point & click.
Next time please attach individual files as files or as an archive of files, not as a text file containing the offending content of your post.
sedi (19th July 2013)
Bookmarks