| Summary: | Kickoff menu not centering on the screen horizontally when centered on the panel and it *could* be centered within existing constraints | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Leniwcowaty <leniwcowaty> |
| Component: | Panel | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | ASSIGNED --- | ||
| Severity: | normal | CC: | 2anwe.0, hypertextcoffee, mikel5764, nate, niccolo.venerandi, niccolo, noahadvs, oat-lip-confront |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=500390 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Expected behaviour shown in Kubuntu 24.04 on Plasma 5.27
Issue still persisting on Plasma 6.3.0 Sadly this is not the case either |
||
|
Description
Leniwcowaty
2025-02-03 18:07:31 UTC
This is fixed for me in Plasma 6.3.0. Created attachment 178602 [details]
Issue still persisting on Plasma 6.3.0
As can be seen - this issue is still present on Plasma 6.3.0
In that case it's also expected: if it centered on the screen, it would no longer appear above the button on the panel. If you un-pin or close some apps, you'll see that it becomes centered as you want. Created attachment 178611 [details]
Sadly this is not the case either
Thank you for your help and assistance.
As can be seen - now I have only 5 icons on my taskbar. If the menu centered on the screen, it would still be above the button. However, the menu still centers on the button, not the screen/panel. Even if the menu is expanded horizontally, it still always center on the button.
In my opinion, it would be beneficial for end user to have a toggle/option to choose if it should center on the button or the screen (similarly to how Andromeda launcher does it)
Hmm, that does seem like a bug based on my understanding of the current implementation. Re-opening! Do I understand correctly, that under current implementation, if: 1. The menu is wide enough, or 2. There aren't enough icons on the panel So that opened menu *could* be both centered and above menu button (fully? partially?) then it should be centered? That seems a bit inconsistent from my point of view. Supposedly I have 5 icons pinned + menu button, and the menu is only wide enough to facilitate 6 icons. Any additional application opened would move the menu button to the left of the panel, which means the menu would no longer be above it. So the menu gets "kicked out" and now centers above the button, completly throwing off the muscle memory, since it opens in completly different place than usual. **A** solution to that is to have the menu be much wider than anticipated number of icons, but in my case that would mean the menu would have to take almost half of the screen width (and I have an ultra-wide monitor, on 16:9 laptop it's almost 3/4 of the screen width). Not very good solution, but it is A solution (of course if it works, which in this case doesn't, at least on both my systems). So if I understand correctly - in current implementation there's no way to FORCE Kickoff to ALWAYS open centered on screen, no matter if it would be above button or not? I got into discussion on Fosstodon with Niccolò Venerandi, who claimed there is an easy-ish way to force that in QML, but sadly the conversation didn't go anywhere from that. Hello there nate@kde.org. Any updates on this? If there was, you'd see it in a comment here. A possibly relevant merge request was started @ https://invent.kde.org/plasma/libplasma/-/merge_requests/1285 (In reply to Bug Janitor Service from comment #9) > A possibly relevant merge request was started @ > https://invent.kde.org/plasma/libplasma/-/merge_requests/1285 This would most likely solve the issue, unfortunately looks like this MR has stalled with no updates in 3 months and its milestone target being Plasma 6.4 no longer applicable. (In reply to Krystian Kacprzak from comment #10) > (In reply to Bug Janitor Service from comment #9) > > A possibly relevant merge request was started @ > > https://invent.kde.org/plasma/libplasma/-/merge_requests/1285 > > This would most likely solve the issue, unfortunately looks like this MR has > stalled with no updates in 3 months and its milestone target being Plasma > 6.4 no longer applicable. I'm sorry about that; we're hitting a weird layershell bug and I haven't found a fix for that yet; but I'll keep trying. (In reply to Niccolò Venerandi from comment #11) > (In reply to Krystian Kacprzak from comment #10) > > (In reply to Bug Janitor Service from comment #9) > > > A possibly relevant merge request was started @ > > > https://invent.kde.org/plasma/libplasma/-/merge_requests/1285 > > > > This would most likely solve the issue, unfortunately looks like this MR has > > stalled with no updates in 3 months and its milestone target being Plasma > > 6.4 no longer applicable. > > I'm sorry about that; we're hitting a weird layershell bug and I haven't > found a fix for that yet; but I'll keep trying. Oh, understandable. Thank you for the response, I just assumed since there are no comments or updates there it just fell into "MR purgatory". Well, nothing to do but be patient I guess! Really looking forward to this being resolved. By the way, it would make for an interesting video, how and why this was changed between 5.27 and 6.0, and why it's this hard going back to how it was! Hi, any progress on this? *** Bug 508825 has been marked as a duplicate of this bug. *** Hello. It has been over 8 months since reporting this, and the issue exists even longer, since 6.0 release. We are past 6.5 release. Is this being worked on? Or has the problem been abandoned? nate@kde.org it would be wiser to answer people whom "dare" to ask, instead of marking them as spam, so totally new people coming by to these tickets would have an actual idea about the progress. Because the way of how you're so diligently marking all these questions as spam (even if they're relevant to the tickets) will cause a chain reaction, of more people coming here to ask around, of what's the status of the ticket, because there's no information. No information => you keep people blindfolded => people will keep asking. So, I ask it aswell (go ahead, mark me as spam, I look forward to it) : are you guys even working on this? If no, thats okay, then just mark the ticket as "later" or something, so people would have an actual idea of what's going on.. There truly is no information, though. The issue hasn't been fixed yet, and the open merge request stalled. Yes, we want to fix it, and there's open work that attempts to, but people get busy, life gets in the way, etc etc etc. And pinging for status updates isn't going to change that, which means it just clutters up the history of the Bugzilla ticket, annoys people who actually read their email, and wastes the time of the people who might be able to fix the issue, making it *less* likely to get fixed. I'm afraid that's just the reality of the situation in a project where work gets done by volunteers (whose motivation is a precious commodity) and sponsored people (whose time is paid for). In this case, what would have helped would have been an explicit reminder about the open merge request. I see that there was an open question, presumably addressed to me, that I forgot to answer. That's my bad, and I've answered it. |