Open leoburn5 opened 1 year ago
Lazarus version? I have encountered such problems, they were introduced and quickly fixed https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/40375
Lazarus version? I have encountered such problems, they were introduced and quickly fixed https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/40375
Can`t confirm((
Can`t confirm((
You have to close IDE, and Open it Again.
The problem seem´s to be related with the dock option "Header Style" = Line or Lines.
I have changed to Themed Button, and it does not happens anymore.
This is a great feature, long waited by us Users, can this be made avaiable online package manager?
No, everything works for me((
online package manager
Of course you can add, but I don't know how to do it. Can you help?
No, everything works for me((
online package manager
Of course you can add, but I don't know how to do it. Can you help?
Sure.
I’ll take a look into it!
I encounter this problem in both versions 2.2.6 and Trunk. Launching Lazarus from the original binary file (Lazarus.exe without any shortcuts on the desktop) triggers the issue. However, when I start it with a shortcut pointing to startlazarus.exe or open it manually, it runs without problems. Furthermore, launching Lazarus.exe with the --no-splash-screen flag also resolves the issue.
Yes, confirm. I have this happening when starting Lazarus with a different settings folder
Does the problem go away when you disable Fill Headers
?
The problem is that there is no mechanism to control the sequence of execution of the package code, at the launch stage of Lazarus, when the folder with the configuration has already been resolved, and initialization has not yet been performed. May be help to change the order of installation of the mds and anchdock packages, but i no check this
Do you know where this initialisation has to be done?
After installing the package, uppon atarting Lazarus, darkmode runs fine.
If I close IDE and start it again, the docked menu bars appears as white as showed belloe:
If I unninstall the package and install again, at first usage, it´s fine, but the problem appears again in the subsequent uses.