General and Desktop

@Karsten-Heimrich said in Qt6Widgetsd.lib dooesn't exist:

qmake version found in D:\Qt\Tools\QtDesignStudio\qt6_design_studio_reduced_version\bin

This is wrong.
You need to select qmake from Qt version you installed. Did you install any Qt version?

@Pl45m4 Hi, I use below code to adjust widget size and the scroll bar is hide.Thank you very much.

QSize sizeTemp = viewport()->size(); testWidget->resize(sizeTemp);

For various reasons I've trashed WSL, so this is no longer an issue :) I've installed an Lubuntu 22.04 build VM

What COM object are you hosting in your MyChildQaxWidget?
If it's something like Internet Explorer, you might be better off using Qt's WebEngine instead.

Thank you all for your help. Based on your analysis, here is my solution,
Create section

auto pTextItem=new QGraphicsTextItem("QGraphicsTextItem",pV); auto id=reinterpret_cast<void*>(dynamic_cast<QGraphicsItem*>(pTextItem));

deletion

void DeleteGraphics(void* id) { if (id==nullptr) return; auto scene=m_pQGraphicsView->scene(); auto items=scene->items(); QGraphicsItem* item = static_cast<QGraphicsItem*>(id); if(items.contains(item)){ scene->removeItem(item); delete item; } }

Posting a solution for those who might encounter the same issue.

As per the suggestion mentioned in the bug report linked in my original post, starting from MacOS Sequoia, the Maintenance Tool app bundle needs to be signed and notarized separately (unless this is fixed in Qt IFW > 4.8).

Fix steps:

use the binarycreator to generate a Maintenance Tool (use your preferred config.xml) sign and notarize the Maintenance Tool yourself implement the logic of replacing the tool as per the Qt IFW documentation in your installscript.qs (provided in previous post) distribute the Maintenance Tool as other packages (your logic may vary here) additionally, you may need to elevate the Maintenance Tool's permissions by executing a chmod +x operation (can be done in your XML config)

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.

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.

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.

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.

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.

@JonB said in QTabWidget - unable to load multiple documents in multiple tabs:

In case that made a difference

In case @blossomsg forgot to implement some function which is needed for QPdfView or so...
Like Q[...]Model derived class without implementing setData

Good that it works now

@abhishek999 You did not answer the second question.

@Gilboonet Oh, OK.