Bug 219057 - [regression]Not possible to remove plasmoid in new add plasmoids dialogue
Summary: [regression]Not possible to remove plasmoid in new add plasmoids dialogue
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-17 12:46 UTC by aapgorilla
Modified: 2009-12-17 14:25 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description aapgorilla 2009-12-17 12:46:59 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

It is not possible to remove a plasmoid like it could be done before, this can be problematic for some widgets because eg. my favorite widget, Ihatethecashew is broken on kde4.4 (please fix it!!!) it has no interface so I couldn't remove it anymore either other than by uninstalling it completely.
Comment 1 Beat Wolf 2009-12-17 12:51:28 UTC
you should report a bug with the maker of that plasmoid(Ihatethecashew). A plasmoid that cannot be removed is obviously broken.
thank you
Comment 2 aapgorilla 2009-12-17 12:54:16 UTC
(In reply to comment #1)
> you should report a bug with the maker of that plasmoid(Ihatethecashew). A
> plasmoid that cannot be removed is obviously broken.
> thank you

well the whole point of I hate the cashew is not to have annoying junk on the screen and this is clearly a regression from kde4.3 and before where it was possible to remove plasmoid centrally from the add(/remove) plasmoids dialogue
Comment 3 Sebastian Kügler 2009-12-17 13:40:18 UTC
This functionality is indeed missing from the new widgets explorer. On the other hand, the functionality was always kind of broken -- try adding more than one plasmoid of the same sort and then try to control which one to remove...

As a plasmoid is a visual UI element, I think it makes sense to assume that it's visual. If a hack (like your "ihatethecashew", which btw removes another set of important functionality) breaks, then the bug should be filed against this plasmoid.

A possible fix for the plasmoid you're talking about would be to make it transparant and put it where the cashew is now, so you don't see it but you can still rmb on it. But that's really up the the author of that plasmoid.
Comment 4 aapgorilla 2009-12-17 13:54:23 UTC
(In reply to comment #3)
> This functionality is indeed missing from the new widgets explorer. On the
> other hand, the functionality was always kind of broken -- try adding more than
> one plasmoid of the same sort and then try to control which one to remove...
> 
> As a plasmoid is a visual UI element, I think it makes sense to assume that
> it's visual. If a hack (like your "ihatethecashew", which btw removes another
> set of important functionality) breaks, then the bug should be filed against
> this plasmoid.
> 
> A possible fix for the plasmoid you're talking about would be to make it
> transparant and put it where the cashew is now, so you don't see it but you can
> still rmb on it. But that's really up the the author of that plasmoid.

This is silly the ihatethecashew was just an example
Comment 5 aapgorilla 2009-12-17 13:57:02 UTC
btw somewhat broken functionality is better than no functionality!
Comment 6 Sebastian Kügler 2009-12-17 14:04:19 UTC
What other plasmoids expose the problem?
Comment 7 aapgorilla 2009-12-17 14:09:11 UTC
(In reply to comment #6)
> What other plasmoids expose the problem?

All of them, for me the problem is there is no a longer a central place to remove them a feature I regularly used for experimenting with new plasmoids but now is no longer present which makes adding and removing them again a cumbersome task
Comment 8 Sebastian Kügler 2009-12-17 14:23:23 UTC
Hm, clicking on a [x] (or right-clicking on a specific item) is a cumbersome task? It follows the "put actions into the context of the object" pretty closely. It might be for you, but given the technical problem I laid out above, I doubt it actually makes sense to put a "remove this plasmoid" into the widgets explorer, at least in the way it was present in its previous incarnation. The problem is that there's not a 1-1 relationship between plasmoids that show up in the widgets explorer and plasmoids on the screen (I actually have a few plasmoids more than once installed, in different activities, different panels, and so on. The new system tray is even specifically designed to support this) Not having a 1-1 relationship, but putting a [x] into the widget explorer leads to confusing (because undefined) behaviour, and that is something we explicitely want to avoid.

Not every removed button is a regression. (But I agree that you might need to get used to it when introducing new things.)
Comment 9 Sebastian Kügler 2009-12-17 14:25:49 UTC
BTW, with the new JavaScripting console in 4.4, it's easy enough to create a list of running plasmoids yourself and removing them. Maybe it's worth investing some time and writing such a small tool, maybe even as its own plasmoid?

http://aseigo.blogspot.com/2009/09/scripting-plasma-desktop.html if you want to know more