I was responding with the top panel edit as you were replying lol. Yes, the top panel does have the same issue.
Edit: Smaller is just my preference as I tend to add many, many launchers onto the dock for quicker access since I use so many programs constantly with programming, school, work, etc. I think the bigger size isn't bad at all if it's more in line with the Garuda theming as it was in Latte layout (which personally I think the bigger size is). If someone wanted to make a smaller dock, it isn't too many clicks away.
Converting from a latte-dock setup to a plasma panel setup (as will happen to most existing dr460nized users in the next release) can now be tested by installing both garuda-dr460nized-next and garuda-system-maintenance-git on an existing system and then relogging/rebooting.
Edit: Garuda-system-maintenance was updated to version 2.0.0, installing garuda-system-maintenance-git is no longer required (neither is it recommended)
kde-unstable is a separate repository of Arch providing pre-release versions of KDE. It has to be placed before core:
[garuda]
Include = /etc/pacman.d/chaotic-mirrorlist
[kde-unstable]
Include = /etc/pacman.d/mirrorlist
[core]
Include = /etc/pacman.d/mirrorlist
Then the new effect not showing up is basically expected and there is no need to worry. Once the new Plasma gets released, it will show up automatically
Nice one, after updating and logging out/in, the highlighting came up immediately. It looks great, snappy too!
It does not uninstall Latte dock, nor does it set up the new dock and panel or change the global theme. Basically the wiki should be used for anyone manually migrating.
You haven't pushed the changes for the default sizes of the dock/panel yet, have you? I tested again on a fresh install, with garuda-dr460nized-next & garuda-system-maintenance-git installed as per @TNE 's guide here and added the second screen top panel/bottom dock, and the sizes are still showing differently than the default garuda-dr460nized-next package dock/top bar.
Edit: Also the default settings for Window Title and Window AppMenu did not set to current screen only by default.
Is there any way to adjust the padding of the bottom dock when a application is maximized (shown below)? The current padding seems a little "fat" to me. The dock is set to be floating by default, but when a window is maximized, it returns to this form.
The only way I know to adjust padding is by resizing the height of the dock, which will eventually shrink or grow the icons so you need to remain within 2 sizes that fit best your taste. I know, there are a few areas where Plasma put some limitations compared to Latte and this is one of 'em.
No, just logged in for the 1st time today. I will look at that within a few days, but also I think there is a delay when a change is applied and the package is available for update in the repo. Never calculated that but it will be a good time to time it.
Maybe eventually this could be a good upstream contribution we could make? I am going to try to get into the code side of Plasma/QT, and learn how to tweak/edit things. Never a good time like the present, right?
Yeah I wouldnât think weâd want to do that. I mean, itâs not unusable in itâs current state, more of a preferential thing for look/feel.
You sure your Button Size in AWCâs Settings is set to 6th notch from the left?
Also you sure you are using the buttons from AWC and not the former Window Buttons applet?
EDIT: I think I have an idea on this issue. When I maximize on one monitor I get this from the 1st:
And that into the 2nd:
EDIT2: Wow⌠just wow. It seems on the second monitor the Button Size has to be 1 notch LESS to equal the 1st monitor. For example if you have 0.6 on the 1st you need 0.5 on the second to have exact sizes matchâŚUnbelievable, but I know how to address that, although totally non-intuitive.
Thereâs a lot weâd want to log at bugs.kde.org. But anyone can open a wishlist there. They do have limitations based on the fact the framework in which Plasma Panel is built from is not the same as Latte, but if we donât open anything we may never get what weâd like. Thatâs how we got the launcher hover feature!
I'll do some thinking through how I want that BR to look like, then go ahead and put that in. Sounds like a rabbit hole of how KDE functions underneath the hood is coming up for me, lol. I want to know how this framework works, the limitations, and how we can remove those limitations. I need to know. Lol Anything useful from those reports I'll report back here.
Seems to work extremely well (why am I not surprised). It is very quick to apply the Theme.
You select NO in the kdialog prompt and you can select the Dr460nized Migration from the dropdown of System Maintenance within the System Tray. It brings the same kdialog back up for a second chance to perform the migration.
The HELP button sends right to the Wiki Migration page. I donât see anything missing in that process, I did question myself about one detail but in the end I would have done it exactly as you did anyway.
I installed a small program last night to fix an issue with VLC after an update.
Nothing to do with Plasma etc.
But Octopi can up with a news item about updating pacman (sudo pacman -Syu base-devel).
There were 70ish updates a lot to do with KDE.
I did them all
Still all good
But anyone can open a wishlist there. They do have limitations based on the fact the framework in which Plasma Panel is built from is not the same as Latte, but if we donât open anything we may never get what weâd like. Thatâs how we got the launcher hover feature!
