Screenlets doesn't remember the correct workspace on restart
Bug #868311 reported by
Diego Lima
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Screenlets |
Fix Released
|
Medium
|
Diego Lima | ||
screenlets (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
After positioning different screenlets in different workspaces and restarting the system/logging off and then on, all screenlets are incorrectly placed on the first workspace. A workaround to this might be using Compiz's "place" plugin, however since the window names do not have unique titles (when using more than one screenlet of the same type) this becomes impossible.
The best solution, IMO, would be if screenlets itself remembered the workspace number, but simply making the window name unique (i.e: instead of "ManometerScree
Changed in screenlets: | |
status: | Triaged → In Progress |
Changed in screenlets: | |
status: | In Progress → Fix Committed |
Changed in screenlets: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I've decided to take a look around Screenlet's code and while I'm not a python expert I figured out the way it loads its Screenlets and I've (manually) done this as a workaround: Instead of loading the Screenlet directly, creat a numbered copy on ~/.screenlets and instead load it. That way we can have "unique" screenlets instead of multiple copies of a single screenlets, each with its own window name (the number).
I'm going to try to implement that in the code, but I'd like to know if that sounds acceptable or too "hackish" (that would solve the positioning problem, though, since I'm now able to use the Place plugin to position each screenlet as I please).