@KroMignon said in How to use Qt documentation?: @Please_Help_me_D said in How to use Qt documentation?: In reality I also need to use Little/Big conversation with float data-type. Do you know how to solve that? As far as I know, a float is stored as a 32 bits word and a double as 64 bits word. So my suggestion would be to cast your float value to quint32 and your double to quint64 float floatBE = static_cast<float>(qToBigEndian(static_cast<quint32>(val)); double doubleBE = static_cast<double>(qToBigEndian(static_cast<quint64>(valDouble)); nope, that does NOT work! Casting float to int truncates it. What you can do instead, is to reinterpret_cast the memory occupied by the float - or use a union. We currently have a similar topic in the forum on this. Regards

@JKSH Thanks, yes I am aware of this possibility in creator. IIRC I had encouraged you to publish the browser extension for Chrome. Great tool! Basically use it all the time. I have stumbled across a couple of macros without a trace of documentation. Personally I consider as a pity.

I am curious on how the clarification will evolve for the topic “Describing build components for CMake support with Qt”.

Sorry mate but I see no point in continuing this conversation. Some software developers agreed that they need the class “variant” for working with type-safe unions. They chose another useful programming interface. These software design decisions might influence other class libraries, don't they? The Qt software library is using also a variant class for the support of the meta-object protocol, isn't it?

@tansgumus said in javascript documentation: Is there any plan to cover JavaScript docs by Qt? Currently not. As I mentioned, the Qt Project has no control over the JavaScript API, so it will not document the JavaScript API either. However, QML classes and methods are fully documented -- if you find something missing, please file a bug report.

Hi, Yes, it's still qdoc that's used, it's also been updated for the QML documentation.

You're welcome ! Since it's all clear now, please mark the thread as solved using the "Topic Tool" button so that other forum users may know an answer has been found :)

Hi, That might be something that have changed between Qt versions. You should go to the bug report system and see if there's already something about it. If not please consider opening a bug for the documentation to be updated on that aspect.

@vishnu Unfortunately I too haven't used the tool myself. Perhaps you to create your own qdocconf configuration file depending upon your requirement. The docs seems to be explaining all the required stuff. Try out the sample conf file mentioned on that page. The tool can be run from anywhere as long as the tool path and conf file path and project paths are valid.

@esekyere after a very short search on google i got this : loader = QUiLoader() file = QFile(":/forms/myform.ui") file.open(QFile.ReadOnly) myWidget = loader.load(file, self) file.close()

Hi and welcome to devnet, You can use QtSdkRepoChooser to try another mirror. Hope it helps

Camera control is not fully implemented yet. There's just a little workaround for this problem for now.

@HarryLong said: I would set this as solved but cannot figure out how... Edit your first message's title to start with [SOLVED].

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