Just add --verbose to the CMake build step. See below for details:

qtcreator-makefiles-verbose.png

Hi,

That's because it's in a layout inside another widget.

On a side note, please format your code properly using coding tags or the </> button in the editing toolbar.

In that case, use a universal build and target both architectures.

Hi,

Is that related to this thread ?

Where in that code is the cropping done ?

Hello everybody,

I'm overlucky: I found the error for myself (-:

The correct code line is now:

emit dataChanged(index(0),index(nparticles-1));

instead of

emit dataChanged(index(0),index(nparticles));

Now I can start working!

Thanks to all!

Tobias

What did you do to fix the problem ?

Hi,

Which version of Qt ?
On which OS ?
Do you have the same issue if the other widget is not a QVideoWidget ?

Hi and welcome to devnet,

One thing that looks wrong is your if condition. 1080p is 1920x1080.

One thing you should try is the latest version of Qt 6. Improvements have happened on the High DPI side.

Hi,

Taking aside the tar issue, macOS rather uses dmg files for distribution. Qt provides macdeployqt which builds such things and that could simplify your life a bit.

You might want to post this question to Qt advanced docking systems github

As a quick solution, you can fix that image using some optimisation utilities.
On the MacOS, I successfully solved this problem using the ImageOptim.
On other platforms, there is some similar tools such as the Trimage for Linux and the pinga for Windows, but I didn't test these.

SOLVED thanks to a previous forum post regarding using MultiEffect on Image{} type component

All that's required is to set VectorImage's visible to false, since the compositor seems to be double rendering, I suppose, creating the unwanted outline of the SVG

Thanks to 6.5 article: https://forum.qt.io/topic/144070/qt6-color-svg-using-multieffect/3
and member: https://forum.qt.io/user/mzimmers

New graphics:
3f636858-1079-499b-9803-afcd8b926c3c-image.png

WORKING CODE:

Item { id: root color: <input from higher level> source: <input from higher> VectorImage { id: mySVG ~~~~ same lines from above ~~~~~ visible: false <======== DONT FORGET THIS } MultiEffect { id: colorOverlay source: mySVG anchors.fill: mySVG colorization: 1.0 // opacity equivalent colorizationColor: root.color } }

Yes. Go to Edit > Advanced > Copy With Highlighting.

You need to have an editor which can handle the highlighting. I just tried it with LibreOffice and worked just fine.

As the responsible person for creating the Qt Desgin Studio packages my view comes from how it is built - not so much how it is used and yes documentation how it can be extend is missing, mostly because we had no requests in that direction until now.

@jsulm said in Qt 6.8.0 - Replacement for QtNative.activity():

@NaLogo Take a look at https://forum.qt.io/topic/159644/qt-6-8-emailsender-activity-is-not-public-in-qtnative-cannot-be-accessed-from-outside-package/6

Like the user in that thread you linked pointed out, it doesn't work like that. The reason for that being what I wrote in my original post: The scope of the method QtNative.activity() in QtNative.java was changed from public to private (by removing the scope) between Qt 6.5 and Qt 6.8

@Parvathy2020 said in Qt 6.8.0 - Replacement for QtNative.activity():

Hi @NaLogo , If you got solution for the above mentioned problem , can you please provide the changes you made to resolve the issue. Thanks in advance !

I haven't tried it yet, but it probably requires an additional call that will pass the activity from the main app to the native class (storing it in a variable, of course) before calling the method you actually want. I'll post the results here when and if I get around to trying it.

What's wrong with QVariant()?

@DungeonLords
In your original code you have

//Write to file write(buf.buffer().constData(), buf_cnt); ... //Choose A) or B) //A) Open-close way // buf.close(); // buf.open(QBuffer::WriteOnly); //B) Clear way buf.buffer().clear();

Because at start you have already written into the buf.buffer() B does not leave you in same state as A. Opening and closing in A resets the current file offset pointer to 0/beginning of file. Just calling buf.buffer().clear(); in B leaves the current file offset pointer where it is, at 2. For B you need to insert buf.seek(0L); either before or after the buf.buffer().clear(); to achieve the same situation, then it will report 1 instead of 2 just like A does.