Qt4 constructors

Nadeem Hasan nhasan at nadmm.com
Wed Sep 7 02:30:32 BST 2005


On Tuesday 06 September 2005 06:45, Harri Porten wrote:
> On Tue, 6 Sep 2005, Benjamin Meyer wrote:
> > yes, setObjectName() is a lot nicer in that regard.  Reading the code
> > you know exactly what it is doing rather then questioning if it is the
> > caption, text or object name.
>
> The problem is that setObjectName() will hardly get used. And for testing
> and scripting the lack of unique object names is really bad. A related
> discussion took place here:

I agree. Object names are required to decipher the signal/slot related error 
messages that Qt spits. Having a separate method to set the name would mean a 
lot of widgets would be "John Doe"s.

-- 
Nadeem Hasan
GPG Fingerprint: 7141 0B1C 9CAF 624D 307F F8EF 6C0C 753E DD3A 0F53
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050906/54962d0f/attachment.sig>


More information about the kde-core-devel mailing list