@SGaist Hi, I'm running Windows 10, OpenGL 4.5.0

Hello!

I faced a similar problem, tried hacks with single QTimer and showEvent: timer was a solution, and showEvent -- wasn't. I also use Win10, but Qt5.5.1. Have you succeeded?

@Wieland said:

Qt.createQmlObject('import QtQuick 2.6; Rectangle {color: "red"; width: 100; height: 100; function nix(){ var arr=["function","two"]; console.log(arr)} Component.onCompleted:nix() }', mainWindow, "dynamicSnippet1");

Good to hear, must be solved then. Thanks!

Finally, I have fresh installed it with Offline Installer, and it's working as expected. It seems isolated, so maybe nothing.

Thank you for having tried ;)

thanks for your anwser

@Wilk said:

The reason that it did not work with QMainWindow or QWidget is that those classes does not implement fullScreen as full featured property - it can not be set with setFullScreen() slot.

I see, thanks for the precision.

@Wilk said:

Thanks alot

No problem, I hope your bug report will be helpful for other people.

@Sargamon
Once your problem is solved please use the Topic Tools button to mark as Solved.
Thank you!

@SGaist

Ok, thanks. I reported it (https://bugreports.qt.io/browse/QTCREATORBUG-15444)
Seems just cosmetic but nonetheless.

It's more of a limitation than a bug I think.

To OS, by default a window is a rectangle, no matter how you paint it, and stylesheets are just a way to paint it.
To cut out the corners you would need a mask. Something like:

auto frame = new QWidget(parent, Qt::Popup); frame->setStyleSheet("background-color: red; border: 1px solid green; border-radius: 6px;"); QPainterPath path; path.addRoundedRect(frame->rect(), 6, 6); frame->setMask(path.toFillPolygon().toPolygon()); frame->show();

The problem is that the mask is a bitmap (0-1), not an image with alpha, so you get a jagged edges, but for some radii it works pretty well.

@jsulm said:

You can check this by typing "groups" in a terminal.

it gave me "root"

@chrisadams No, there is no change at all with QML_NO_TOUCH_COMPRESSION enabled

Nevermind I found a solution:

QQmlApplicationEngine::setObjectOwnership(MY_OBJECT*, QQmlApplicationEngine::CppOwnership);

It's important to set this whenever returning a pointer in a Q_INVOKABLE function or else it might get garbage collected apparently.

I had an old mouse that gave irratic scroll wheel signals. It still worked but I did notice it jumpy when trying to scoll windows on occasion (all windows, not just Qt). I don't know what you are using but I would make sure the problem is not hardware.

I don't know why it's hard to understand that it shouldn't register ALT-GR as CTRL+ALT just register it simply ALT or a different type of ALT but not CTRL+ALT (or atleast put an option there).

What version of Ubuntu are you running ?

Did you test with the version of Qt Creator from Ubuntu's repositories ?

I know, and I want to, but I don't think I can because I can't create a good compilable example that reproduces the error. If you simply create a dockWidget that has a listView and you try to scroll it is fine. Even though I tried to configure it the same way.
I am not sure what exactly in my app triggered this bug.

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