Subject: [Development] Extending Visual Studio's display of Qt classes
>
> I understand why the Pimpl Idiom is being used here, but I'm wondering
> if it's actually necessary. It's intended for when the source code of
> the implementation isn't available so internal varia
To: Tom Isaacson
Cc: development@qt-project.org
Subject: Re: [Development] Extending Visual Studio's display of Qt classes
> It's intended for when the source code of the implementation isn't available
> so internal variables and function names can be completely hidden.
That i
> It's intended for when the source code of the implementation isn't available
> so internal variables and function names can be completely hidden.
That is not the motivation at all in Qt's case. The reasons for it are:
- Binary compatibility between minor Qt versions. Adding, removing or
cha
I've been working on some networking code recently and I got very frustrated
with not being able to see the IP and MAC addresses in QHostAddress and
QNetworkInterface whilst debugging in Visual Studio. After a bit of
experimentation I was able to add viewers for these classes to autoexp.dat and
