Maybe you can make a generic DummyScreenletNN.py (or whatever name you need) calling to WhateverScreenlet.py, because it's good NOT to have many of the same actual screenlets in system. I think, it would cause trouble when updating a screenlet version and/or render modifying the screenlet code very obscure. What about starting screenlet from command prompt, will your planned changes apply to this situation too?
I remember that there is some python (or c) module to change file name/identifier when the file is running. I don't remember the name of the module now (and I don't know if this will work for Compiz plugins), but this might be usable for implementing your idea. Maybe you can go for much less hackish solution this way... If I recall the name of the module, I'll let you know. -- You received this bug notification because you are a member of Screenlets Dev Team, which is subscribed to Screenlets. https://bugs.launchpad.net/bugs/868311 Title: Screenlets doesn't remember the correct workspace on restart To manage notifications about this bug go to: https://bugs.launchpad.net/screenlets/+bug/868311/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~screenlets-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~screenlets-dev More help : https://help.launchpad.net/ListHelp
