search

Razor-qt / razor-qt

Razor is now LXQt:
http://lxqt.org
Other
366 stars 78 forks source link

Height issue with new panel after reboot #571

Closed jleclanche closed 10 years ago

jleclanche commented 11 years ago

http://i.imgur.com/lo1DefJ.png

Nanolx commented 11 years ago

For me this issue is fixed by latest commits fixing bug #564

diggit commented 11 years ago

I must agree with Adys. It happens with latest build. Height of panel is is increased by taller plugins such as: date & time, CPU usage, maybe other more. Some plugins does not accept this change a remains at panel's minimum height, mainly: task manager, application menu and tray (probably not only those).

jleclanche commented 11 years ago

From my screenshot this is caused by the color picker plugin; it's apparently two rows high instead of one or something similar.

diggit commented 11 years ago

Color pickers is high (reason is not important), expected panel behavior is height increase to fit it, it happens. IMHO other plugins should increase their heights according to highest plugin,but this respects only "Desktop switcher". All remaining plugins have their height controlled by panel height settings. As described above, this value is NOT correct, because some plugin forced to panel different height to fit in panel. Now you could fix this weird look of panel by increment of his height in panel options by hand. This wrong behavior of plugins should be fixed, maintainers?

diggit commented 11 years ago

That is interesting, my panel config disappeared and went info default one. Everything is OK now! Probably panel's config file was somehow corrupted and IMHO this commit 9f7b09cc3ab2292dc1b1f6b7ff01368fa322c86f solved it. Adys: Try to delete your panel config or better, update your razor-qt.

jleclanche commented 11 years ago

As I said, this is because of the plugins that are in the panel.

diggit commented 11 years ago

You are right, CPU load, Color picker and maybe other high plugins still does problems. They are not in default config :D That is why it looked like fixed

jleclanche commented 10 years ago

This was fixed.