mirror of
https://github.com/qmlnet/qmlnet.git
synced 2026-05-16 14:15:57 -06:00
[GH-ISSUE #77] UI lag when resizing UI #48
Labels
No labels
bug
enhancement
help wanted
help wanted
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/qmlnet#48
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @codec-abc on GitHub (Nov 4, 2018).
Original GitHub issue: https://github.com/qmlnet/qmlnet/issues/77
Hi,
I wanted to try this out and ran into performance issues when resizing a very basic app.
Disclaimer, I don't know QML/QT, and have little experience with on .Net Core.
Basically, I created a simple .Net Core app with the following single cs file:
and my
Main.qmlcontains the following:When resizing the UI lags quite heavily because the window cannot keep the resizing movement. By the way, I am running Windows 10.
@pauldotknopf commented on GitHub (Nov 4, 2018):
You are currently running pure QML, so the problem isn't related to this project.
With that said, there is probably an issue with your Windows install. What graphics card are you using? Are you drivers updated?
Do you run into perf problems running this project?
@pauldotknopf commented on GitHub (Nov 4, 2018):
Read this: http://doc.qt.io/qt-5/windows-requirements.html
Try to set
QT_OPENGL=anglebefore launching the app.@codec-abc commented on GitHub (Nov 4, 2018):
The sample crash with an Access Violation message. I have a GTX 1070 with version 388.43 for the driver.
@codec-abc commented on GitHub (Nov 4, 2018):
The
QT_OPENGL=anglesolved the lag. However, it is a bit disappointing that a QT (a framework that is a few decade old) does not run well out of the box.Thanks for the help.
@pauldotknopf commented on GitHub (Nov 4, 2018):
Glad you got it sorted!