
Originally Posted by
jacek
Behavior of the "frame" property depends on the current style and has nothing to do with the platform.
The Assistant states:
By default, QLineEdits have a frame as specified by the Windows and Motif style guides; you can turn it off by calling setFrame(false).
By default, QLineEdits have a frame as specified by the Windows and Motif style guides; you can turn it off by calling setFrame(false).
To copy to clipboard, switch view to plain text mode
So the "frame" setting is just switching between the Windows and Motif style guides. The various settings associated with QStyle are not settable in the Designer, so in Windows a depression turns on or off, and in Linux a line turns on or off, when you toggle the frame setting.
Even IF QStyle changes were available in the Designer, the fact that the Designer lacks a group select capability where a group of identical widgets (or a group with similar properties) can be selected and the value of a property can be changed for all of them at one time, forces one to change each widget one at a time, manually. Filling up your class constructor with hand coded custom widget classes for over 100 widgets isn't very productive. I've even tried editing the app.ui manually to add or change features, but that is more witchcraft than coding, especially when you end up with a message that says
'' is not a valid widget
'' is not a valid widget
To copy to clipboard, switch view to plain text mode
and you can't find "". Then you revert to backup and try a different tack.
Subclassing QLineEdit with QStyle just to manipulate the style properties isn't my idea of productive coding. I started down that road with Visual Fox Pro 5.0 by subclassing all the controls so I could add my special features to them. The next time MS released an upgrade to fix bugs in the controls I was stuck. I either had to overwrite my controls with the upgrade, losing my features, or forgo the bug fixes. I decided to go with the bug fixes. In the long run it made maintanence a LOT easier.
In fact, Qt's "rich" widget set is only available via hand coding. The various settings for each widget that the Designer makes available reduce the graphical interface to "crude" rather than "rich", because the tools the Designer supplies to manipulate the widgets are rudimentary at best. But, the widgets are "good enough" to do what I need to get done. I am counting on the fact that the "richness" accessable through the designer, and the power of the Designer, will only improve as time goes on.
Bookmarks