[Qt-interest] Are there any disadvantages with OT

[BRM]

----- Original Message ----

> From: David Ching <dc at remove-this.dcsoft.com>
> There's a difference between having 
> the skills to find out and needing 
> prerequisite knowledge of internals 
> before using them.  We'd all be in lost 
> if we needed to know how an 
> engine converted fuel into power before driving 
> a car.  It simply 
> doesn't matter.  Likewise, I shouldn't have to know how to 
> deal with 
> QStyle and stylesheets before using QWidget!  But I am more 
> valuable as 
> a programmer if I can find out when needed.

You do not need to know any Qt internals to use Qt.
QStyle and stylesheets are not Qt internals, btw; and information on them is published in the Qt documentation.

> In fact I said I needed to 
> learn Qt internals in order to create derived 
> classes that worked around Qt 
> bugs.  This is necessary in Qt more than other 
> frameworks, so I do know 
> how to dive into framework internals.  Still, I 
> prefer to buy pre-made 
> components that I can treat as a black box to save 
> some time, relying on my 
> debugging ability to make them work for me.

BTW, it is likely only a perceived "bug", but...

Funny you should mention anything that way.
This has been Microsoft's bane for a long long time.
They have been so slow to fix issues in their system that developers have historically done workarounds.
Now, anytime Microsoft attempts to fix something, they also have to test thousands of applications to see what breaks,
and often they try to fix that application too.

So, even if this was valid (which I highly doubt) then it still doesn't hold a candle to the same problem under the Windows API.

And, btw, referencing any internals (e.g. the various private classes inside the Qt API that are not publicly documented) puts you in unsupported territory.

Ben