QXListView - 'Active List' Demo

[jpn]

Remember the only two valids include schemes for Qt headers are suffixed lowercase and not suffixed class-like capitalized names... Mixing both may work on some platforms but not on all...

Well actually, it's perfectly valid to mix those two schemes. If you take a look at various Qt source files you'll see that Qt itself does so. Every proper Qt installation on all supported platforms has both header file types. Non-suffixed camel cased - so called convenience header files - are there just to forward the inclusion to corresponding suffixed lower cased header files.

[rickbsgu]

Well actually, it's perfectly valid to mix those two schemes. If you take a look at various Qt source files you'll see that Qt itself does so. Every proper Qt installation on all supported platforms has both header file types. Non-suffixed camel cased - so called convenience header files - are there just to forward the inclusion to corresponding suffixed lower cased header files.

Crawling around in the source, that's what I noticed, as well.

Thanx,
rickb

[fullmetalcoder]

Every proper Qt installation on all supported platforms has both header file types. Non-suffixed camel cased - so called convenience header files - are there just to forward the inclusion to corresponding suffixed lower cased header files.

I've been using prebuilt packages for the last three distros I used and none of them featured mixed includes... I guess they've removed them AFTER building the bins. Better to have it working on all possible configurations anyway.

[jpn]

I've been using prebuilt packages for the last three distros I used and none of them featured mixed includes... I guess they've removed them AFTER building the bins. Better to have it working on all possible configurations anyway.

Erm, what do you actually mean with mixed includes? Both of these work on every supported platform:

#include <QObject>
#include <qobject.h>

#include <QObject>
#include <qobject.h>

To copy to clipboard, switch view to plain text mode 

However, due to case sensitive file systems, you cannot do something like this:

#include <qobject>

#include <qobject>

To copy to clipboard, switch view to plain text mode 

As already stated, include <QObject> does nothing but further includes <qobject.h>. Lower case header files simply cannot be removed. Without them you have no declarations at all. And why would any distro remove convenience headers?

What you say makes no sense to me. It would mean that it was never safe to use either include scheme.

[rickbsgu]

I might be doing the latter - although it builds on all three platforms in my environment. I'll check, again, but not for a bit. I'm a bit buried in the process of making a big demo for a prospective client.

Later,
rickb

[fullmetalcoder]

Erm, what do you actually mean with mixed includes?

Well, basically this :

#include <qobject>

#include <qobject>

To copy to clipboard, switch view to plain text mode 

Remember the only two valids include schemes for Qt headers are suffixed lowercase and "not suffixed" class-like-capitalized names... Mixing both may work on some platforms but not on all...

I thought my above statement had been clear enough as to where the problem lies but I may have missed something due to my poor english skills... If so please let me know. Actually I don't think any files were removed. This was just a supposition I made after reading your previous post a bit too fast...

Hoping it makes more sens to you now.