Open Qmlio opened 1 year ago
"The maximization state is lost" is an ancient Qt Quick bug and it's still not fixed (latest dev code). I added workaround to Frameless(Application)Window so it doesn't have this issue. If you really care about this issue, please use Frameless(Application)Window instead.
I added "won't fix" label due to not fixable from my side. It's a QtQuick bug after all.
Ok....i guess i will use that... thanks for the help
On Fri, Nov 17, 2023, 12:57 Yuhang Zhao @.***> wrote:
I added "won't fix" label due to not fixable from my side. It's a QtQuick bug after all.
— Reply to this email directly, view it on GitHub https://github.com/wangwenx190/framelesshelper/issues/324#issuecomment-1816067291, or unsubscribe https://github.com/notifications/unsubscribe-auth/APVSHJAF74ROHDHEDNE3S5DYE4YJXAVCNFSM6AAAAAA7PG3QXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJWGA3DOMRZGE . You are receiving this because you authored the thread.Message ID: @.***>
Greeting I really like this repo and it has helped me a lot, i have noticed an issue when minimizing and restoring a Qt Quick window when using when using the ApplicationWindow component from Qt controls, i hope the video can give a better description. as you notice, if i use the FramelessApplicationWindow component and first maximize the window, then i minimize it , then later i restore it from the task bar, its original state is reserved (maximized state), but if i change the root component to ApplicationWindow and repeat the same process, its original state is not reserved... any help or work around is much appreciated. Am using Qt 6.5.1, MSVC 2019.
https://github.com/wangwenx190/framelesshelper/assets/65741732/608ea207-5a67-4d8f-91a6-79c6382ab6eb