https://bugs.kde.org/show_bug.cgi?id=391578
--- Comment #8 from Nate Graham <n...@kde.org> --- Tricky problem. The last-added instance, maybe? That's what seems to happen right now. The only bug is that control doesn't shift back without restarting plasmashell. To me that seems like a reasonable-enough solution until we can do a larger re-architecture of this. Or just spitballing here: If you already have one instance and you add a second, could the second basically just act as a link to the first one, or use its configuration data? I'm not sure what the value is in having multiple volume plasmoids when they each have different settings. In fact I do set the maximum volume above 100%, and I was confused when I added the second one to see what it was and I found that it had the volume set back to 100% again. I expected it to inherit the configuration data from the original. Is there a use case for having multiple Plasmoids with different configuration data, or is this just a quirk of the implementation? -- You are receiving this mail because: You are watching all bug changes.
