I do not know whether this is the right place, but I wanted to ask if you have the sistem tray, and the icon of amarok that the icon of the media player is a normal thing, or whether it would be better to have only a default, to avoid redundancy

lazyit wrote:I do not know whether this is the right place, but I wanted to ask if you have the sistem tray, and the icon of amarok that the icon of the media player is a normal thing, or whether it would be better to have only a default, to avoid redundancy

I'm not sure where you would put that, but I know one thing you can do is go into the tray settings and either set the Amarok entry to always hide, or remove the media player.

It is true, which is actually a pretty simple solution, but it would be nice if this problem did not exist, in KDE 4, there was a default plasmoid dedicated to the media player and so this problem did not arise, then the icons Amarok were designed when the media player of plasma did not exist in the system tray!
Anyway thanks for the reply and sorry if sometimes the things I point out are stupid, but you try to help as I can

lazyit wrote:It is true, which is actually a pretty simple solution, but it would be nice if this problem did not exist, in KDE 4, there was a default plasmoid dedicated to the media player and so this problem did not arise, then the icons Amarok were designed when the media player of plasma did not exist in the system tray!
Anyway thanks for the reply and sorry if sometimes the things I point out are stupid, but you try to help as I can

No such thing as a stupid question.

(now that I've said that somebody, somewhere, will immediately test me on that quote)

It would definitely be good though for a future polish session to tackle things like redundancies, but we'll need to pay attention to ensure we aren't going distro-specific. E.g. I don't know if all distros bundle Amarok with KDE, so some might not have that problem. Either way it's not so much of a visual issue as much as it's a functional one, but I think it would be worth focusing on things like that in the future specifically.

What I find rather confusing, the amarok and the media player tray icon behave different.
With the amarok icon you need to right click for the quick commands menu, with the media player its a left click.

The same is pretty much true for all the tray icons. You actually have to know, whats is a application try icon and what is an plasmoid(?) icon. Even after using Plasma 5 for quite some time I still click wrong most the time if I don't think before hand.
Maybe it would be good to reconsider how try icons behave. I think this has been discussed before, but I couldn't the thread anymore.

What do you think of this Plasmoid, partly looks very nice, but those buttons giants seem a little strange, I would love to see a mockup with buttons and alignments reset so different, I think could improve enough, what do you think?

Just a minor thing but it would add a bit of polish (and return a bit of functionality that seems to have disappeared)!

When you insert a storage device such as a USB stick, the device notifier pane pops up from the panel. If you haven't set it to auto-mount then a green circular button with a white tick in it appears to the right of the entry for that device, clicking it mounts that new device. There's a couple of seconds delay between clicking that green 'mount' icon and the USB drive being mounted - after it's mounted the 'mount' icon changes into an eject icon - click on that to eject the device.

In 4.x there was feedback between clicking the 'mount' icon (it was a black & white icon with a USB cable) and the 'eject' icon appearing so that you knew that it was in the process of mounting the device - the 'mount' icon was replaced with a spinning green thing. In Plasma 5 there's no feedback so you click the 'mount' icon and then are left wondering if the click registered and if you should click again - some feedback that the click was registered and that you're just waiting for the device to be mounted like in 4.x would be good!

Apologies - i forgot to say that i was using Opensuse (the dark theme), that's why i was referring to the 'mount' icon being a green circle with the white tick in it.

The issue of not having feedback when the 'mount' icon has been clicked is still an issue whatever theme or icons are used though....

Breeze-dark colour theme. Effects settings window. Is this an issue? Will it be fixed?

iostapenko wrote:
Breeze-dark colour theme. Effects settings window. Is this an issue? Will it be fixed?

I can confirm this problem, as I'm also using one of the dark color schemes now. It seems this menu changes text color accordingly, but without changing its background color equivalent as well... therefore we get white text on a white background, instead of white text on a dark gray background.

Thats a bug. Definitly a bug. Should be reported as such (to kwin). I believe this is related to the use of QML for creating this list.

I have half a patch for that locally. The remaining problem is that the buttons paint using the global color, so you can run into invisible (or invisibly checked) checkboxes.
And yes: it /is/ one of the many QML issues

So, after a long break from the GTK theme, I've managed to get the menus consistent with what Hugo has shown.

GTK 3:



GTK 2:



After wrestling with the GTK 2 pixmap engine for a while, I found leaving the grey border was the most acceptable solution for the moment.

ScionicSpectre wrote:So, after a long break from the GTK theme, I've managed to get the menus consistent with what Hugo has shown.

GTK 3:

*boop*

GTK 2:

*beep*

After wrestling with the GTK 2 pixmap engine for a while, I found leaving the grey border was the most acceptable solution for the moment.

GTK2 is largely being phased out and the "big apps" are GTK3 now anyway; I wouldn't give it high priority, I don't think it's worth stressing over IMHO.

Kver wrote:GTK2 is largely being phased out and the "big apps" are GTK3 now anyway; I wouldn't give it high priority, I don't think it's worth stressing over IMHO.

I tend to agree. I'll do what I can up to a point with GTK 2, but it's ultimately not going to be the part of Breeze most users are looking at. I don't think it's worth writing a theme engine over, for instance.