You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note, while version of LMMS is different than default master and it is personal fork, it didn't contain changes in reported area.
Second note, it could be just result of trying to display really big window in 1080p screen.
Expected Behaviour
Perfect situation would be to not have warnings on start, but here I am not sure.
Steps To Reproduce
In my case I first build lmms using MSYS2
Start lmms with QT_SCALE_FACTOR=4 on 1080p screen.
Logs
Click to expand
`$ QT_SCALE_FACTOR=4 ./lmms
Lv2 plugin SUMMARY: 0 of 0 loaded in 0 msecs.
setGeometry: Unable to set geometry 3060x1936+0+28 (frame: 3078x1983-9-10) on QWidgetWindow/"lmms::gui::MainWindowClassWindow" on "\.\DISPLAY1". Resulting geometry: 1920x991+0+29 (frame: 1938x1038-9-9) margins: 9, 38, 9, 9 minimum size: 765x484 MINMAXINFO maxSize=0,0 maxpos=0,0 mintrack=3078,1983 maxtrack=0,0)
Error while determining PE file's machine type: Cannot map file
QWidget::setMinimumSize: (/lmms::gui::PositionLine) Negative sizes (0,-44) are not possible
QWidget::setMaximumSize: (/lmms::gui::PositionLine) Negative sizes (16777215,-44) are not possible
QWidget::setMinimumSize: (/lmms::gui::PositionLine) Negative sizes (0,-44) are not possible
QWidget::setMaximumSize: (/lmms::gui::PositionLine) Negative sizes (16777215,-44) are not possible
QWidget::setMinimumSize: (/lmms::gui::PositionLine) Negative sizes (0,-44) are not possible
QWidget::setMaximumSize: (/lmms::gui::PositionLine) Negative sizes (16777215,-44) are not possible
setGeometry: Unable to set geometry 4192x2472+0+28 (frame: 4210x2519-9-10) on QWidgetWindow/"lmms::gui::MainWindowClassWindow" on "\.\DISPLAY1". Resulting geometry: 1920x991+0+29 (frame: 1938x1038-9-9) margins: 9, 38, 9, 9 minimum size: 1048x618 MINMAXINFO maxSize=0,0 maxpos=0,0 mintrack=4210,2519 maxtrack=0,0)
QWidget::setMinimumSize: (/lmms::gui::PositionLine) Negative sizes (0,-44) are not possible
QWidget::setMaximumSize: (/lmms::gui::PositionLine) Negative sizes (16777215,-44) are not possible
QWidget::setMinimumSize: (/lmms::gui::PositionLine) Negative sizes (0,-44) are not possible
QWidget::setMaximumSize: (/lmms::gui::PositionLine) Negative sizes (16777215,-44) are not possible
QWidget::setMinimumSize: (/lmms::gui::PositionLine) Negative sizes (0,-44) are not possible
QWidget::setMaximumSize: (/lmms::gui::PositionLine) Negative sizes (16777215,-44) are not possible
setGeometry: Unable to set geometry 3356x2472+0+28 (frame: 3374x2519-9-10) on QWidgetWindow/"lmms::gui::MainWindowClassWindow" on "\.\DISPLAY1". Resulting geometry: 1920x991+0+29 (frame: 1938x1038-9-9) margins: 9, 38, 9, 9 minimum size: 839x618 MINMAXINFO maxSize=0,0 maxpos=0,0 mintrack=3374,2519 maxtrack=0,0)
QWidget::setMinimumSize: (/lmms::gui::PositionLine) Negative sizes (0,-44) are not possible
QWidget::setMaximumSize: (/lmms::gui::PositionLine) Negative sizes (16777215,-44) are not possible
`
Screenshots / Minimum Reproducible Project
No response
Please search the issue tracker for existing bug reports before submitting your own.
I have searched all existing issues and confirmed that this is not a duplicate.
The text was updated successfully, but these errors were encountered:
System Information
Windows 11
LMMS Version(s)
LMMS 1.3.0-alpha.1.794+468db3a
Most Recent Working Version
No response
Bug Summary
Note, while version of LMMS is different than default master and it is personal fork, it didn't contain changes in reported area.
Second note, it could be just result of trying to display really big window in 1080p screen.
Expected Behaviour
Perfect situation would be to not have warnings on start, but here I am not sure.
Steps To Reproduce
In my case I first build lmms using MSYS2
Start lmms with QT_SCALE_FACTOR=4 on 1080p screen.
Logs
Click to expand
Screenshots / Minimum Reproducible Project
No response
Please search the issue tracker for existing bug reports before submitting your own.
The text was updated successfully, but these errors were encountered: