Thank you Chris.

I solved it by generating a text file with instructions in vbscript and executing it afterwards. With this variant I can manipulate word documents more easily but it only works for Windows.

It's not that efficient but I have a lot more documentation for working with word.application in vbscript.

I reiterate my thanks for answering me so quickly.

@jsulm I wrote the error message

Bonsoir,

Non, de plus sur Android et iOS, ce sont les composants systèmes qui sont utilisés.

@sierdzio Many thanks!

I have written the following code:

if (fileEndian == "Little"){ for(quint32 i = 0; i < nTrc; i++){ FFID(i) = *util::bit_cast<qint32*>(qFromLittleEndian(qFile->map(3608+i*bytesPerTrc, 1))); } } else if (fileEndian == "Big"){ for(quint32 i = 0; i < nTrc; i++){ FFID(i) = *util::bit_cast<qint32*>(qFromBigEndian(qFile->map(3608+i*bytesPerTrc, 1))); } }

It gives me errors:

readsegy.obj:-1: ошибка: LNK2019: unresolved external symbol "unsigned char * __cdecl qbswap<unsigned char *>(unsigned char *)" (??$qbswap@PEAE@@YAPEAEPEAE@Z) referenced in function "unsigned char * __cdecl qFromBigEndian<unsigned char *>(unsigned char *)" (??$qFromBigEndian@PEAE@@YAPEAEPEAE@Z) debug\ReadSegy.exe:-1: ошибка: LNK1120: 1 unresolved externals

The compilator output:
jom: C: \ Users \ tasik \ Documents \ Qt_Projects \ build-ReadSegy-Desktop_x86_windows_msvc2017_pe_64bit-Debug \ Makefile.Debug [debug \ ReadSegy.exe] Error 1120
jom: C: \ Users \ tasik \ Documents \ Qt_Projects \ build-ReadSegy-Desktop_x86_windows_msvc2017_pe_64bit-Debug \ Makefile [debug] Error 2
19:05:31: The process "C: \ Qt \ Tools \ QtCreator \ bin \ jom.exe" ended with code 2.
Error during assembly / deployment of ReadSegy project (bundle: Desktop (x86-windows-msvc2017-pe-64bit))
During the execution of the "Assembly"

Actually the problem was that I didn't know the line which throws these errors but by intuation I just commented the BigEndian part of the code and it works:

if (fileEndian == "Little"){ for(quint32 i = 0; i < nTrc; i++){ FFID(i) = *util::bit_cast<qint32*>(qFromLittleEndian(qFile->map(3608+i*bytesPerTrc, 1))); } } else if (fileEndian == "Big"){/* for(quint32 i = 0; i < nTrc; i++){ FFID(i) = *util::bit_cast<qint32*>(qFromBigEndian(qFile->map(3608+i*bytesPerTrc, 1))); }*/ }

I use little endian Windows 10 x64, Qt 5.14.0, MSVC 2017 x64.
Why do I can use qFromLittleEndian but I can't qFromBigEndian??

By the way the endian of my file is LITTLE now

I think I just found a solution. If I change the order of performing bit_cast and qFromBigEndian it works:

if (fileEndian == "Little"){ for(quint32 i = 0; i < nTrc; i++){ FFID(i) = qFromLittleEndian(*util::bit_cast<qint32*>(qFile->map(3608+i*bytesPerTrc, 1))); } } else if (fileEndian == "Big"){ for(quint32 i = 0; i < nTrc; i++){ FFID(i) = qFromBigEndian(*util::bit_cast<qint32*>(qFile->map(3608+i*bytesPerTrc, 1))); } }

I don't understand why but that works fine

@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 In a project called RBIMS, I created a text docuemt called RBIMS.qdocconf which contained the following text:

include(compat.qdocconf) project = RBIMS outputdir += ./html headerdirs += . sourcedirs += . exampledirs = . imagedirs = ./images headers.fileextensions = "*.h *.ch *.h++ *.hh *.hpp *.hxx" sources.fileextensions = "*.cpp *.qdoc *.mm *.qml"

I used the following command (executed from within my project folder) at the command line:

~/Qt/5.15.0/gcc_64/bin/qdoc /home/jim/Qt_Projects/RBIMS/RBIMS.qdocconf

This produced an XML file in the html folder inside my project.

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE QDOCINDEX> <INDEX url="" title="RBIMS Reference Documentation" version="" project="RBIMS"> <namespace name="" status="active" access="public" module="rbims"> ... ... Code removed for brevity ... virtual="non" const="false" static="false" final="false" override="false" type="bool" signature="bool createDatabase()"/> <function name="database" fullname="database::database" href="database.html#database" status="active" access="public" location="database.h" filepath="/home/jim/Qt_Projects/RBIMS/database.h" lineno="36" documented="true" meta="constructor" virtual="non" const="false" static="false" final="false" override="false" type="" brief="Database::database test constructor doc parent" signature="database(int *parent)"> <parameter type="int *" name="parent" default="nullptr"/> </function>

You can see (toward the end) that ....

brief="Database::database test constructor doc parent"

is created, which was a

/*! * \brief database::database test constructor doc * \param parent */

Qdoc comment in my code.

@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].