Hi,

Qt3D is a tech-preview, rest assured that the documentation will be there when it's officially integrated.

I don't think the fix for this situation is sprinkling the docs with "is always greater than or equal to 0". I don't really think there is a doubt in someones head about whether or not a size or length function returns negative value no matter if it's unsigned int, qint64 or size_t.
I think the opposite is more reasonable - document cases where it can actually return negative value and what it means, which Qt docs are doing pretty consistently (correct me if I'm wrong).

You are probably right. I have added a report on JIRA

@Tusharh
Hi and welcome to devnet

A featrure as you request may be latest with larger projects too much for the debugger to handle.

The closest to get such a behaviour is to use F11 and Shift+F11. F11 will enter every possible method and Shift+F11 will help you to run the remainder of the method. IMO sufficient enough to get a really detailed anaylsis of source code.

Hi,

Technically putting the Q_OBJECT macro without using any signals or slots does not really make sense. Anyway, you can create a templated QObject without using the Q_OBJECT macro.

The Qt Quarterly number 15 talks about that.

Hope it helps

@koahnig thanks, closed those as requested.

Thank you for sharing this info