Workspace support

Asked by Robert Withers

Hi, great work!

I'm using Ubuntu 12.10 with Compiz and Unity enabled.

Are screenlets supposed to be stuck on workspace 1 if autostarted? I haven't been able to find anything recent on it, just year old stuff where Unity support was still not integrated.

I'd love to have webframes locked in on different workspaces so I could flick through, but if I have to start it manually each boot it's not really worth it.

I've tried to hack the .ini files with a script at startup, changing the x and y values to roll onto the other screens with a sed call, but the webframe screenlet somehow gets reset to the center of workspace 1 automatically. The terminal and folderview screenlets work fine.

If workspaces aren't supposed to be working, do you know why the webframe screenlet gets reset? Is it something to do with GTK or Compiz, or the screenlet itself? Just wondering if I can hack it.

Thanks, if you took the time to read it. I love what you're trying to do

Question information

Language:
English Edit question
Status:
Solved
For:
Screenlets Edit question
Assignee:
No assignee Edit question
Solved by:
Robert Withers
Solved:
Last query:
Last reply:
Revision history for this message
Rastko Karadzic (rastkokaradzic) said :
#1

Hm, that's weird, they should snap to selected workspace like normal
screenlets. Which version are you using? Are cordinates in ini files
reseted to the central position or just they aren't parsed correctly?
On Oct 24, 2012 11:35 AM, "Robert Withers" <
<email address hidden>> wrote:

> New question #212173 on Screenlets:
> https://answers.launchpad.net/screenlets/+question/212173
>
> Hi, great work!
>
> I'm using Ubuntu 12.10 with Compiz and Unity enabled.
>
> Are screenlets supposed to be stuck on workspace 1 if autostarted? I
> haven't been able to find anything recent on it, just year old stuff where
> Unity support was still not integrated.
>
> I'd love to have webframes locked in on different workspaces so I could
> flick through, but if I have to start it manually each boot it's not really
> worth it.
>
> I've tried to hack the .ini files with a script at startup, changing the x
> and y values to roll onto the other screens with a sed call, but the
> webframe screenlet somehow gets reset to the center of workspace 1
> automatically. The terminal and folderview screenlets work fine.
>
> If workspaces aren't supposed to be working, do you know why the webframe
> screenlet gets reset? Is it something to do with GTK or Compiz, or the
> screenlet itself? Just wondering if I can hack it.
>
> Thanks, if you took the time to read it. I love what you're trying to do
>
> --
> You received this question notification because you are a member of
> Screenlets Dev Team, which is an answer contact for Screenlets.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~screenlets-dev
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~screenlets-dev
> More help : https://help.launchpad.net/ListHelp
>

Revision history for this message
Rastko Karadzic (rastkokaradzic) said :
#2

I have tried now on Debian squeeze (gnome3 fallback) and webrames are
working fine, but i'm using 0.1.7 dev version. Can you try your version on
Unity 2D and, if it doesnt work, try 0.1.7 version from PPA. Thanks.

Rastko Karadzic
On Oct 24, 2012 5:16 PM, "Rastko Karadzic" <
<email address hidden>> wrote:

> Question #212173 on Screenlets changed:
> https://answers.launchpad.net/screenlets/+question/212173
>
> Status: Open => Answered
>
> Rastko Karadzic proposed the following answer:
> Hm, that's weird, they should snap to selected workspace like normal
> screenlets. Which version are you using? Are cordinates in ini files
> reseted to the central position or just they aren't parsed correctly?
> On Oct 24, 2012 11:35 AM, "Robert Withers" <
> <email address hidden>> wrote:
>
> > New question #212173 on Screenlets:
> > https://answers.launchpad.net/screenlets/+question/212173
> >
> > Hi, great work!
> >
> > I'm using Ubuntu 12.10 with Compiz and Unity enabled.
> >
> > Are screenlets supposed to be stuck on workspace 1 if autostarted? I
> > haven't been able to find anything recent on it, just year old stuff
> where
> > Unity support was still not integrated.
> >
> > I'd love to have webframes locked in on different workspaces so I could
> > flick through, but if I have to start it manually each boot it's not
> really
> > worth it.
> >
> > I've tried to hack the .ini files with a script at startup, changing the
> x
> > and y values to roll onto the other screens with a sed call, but the
> > webframe screenlet somehow gets reset to the center of workspace 1
> > automatically. The terminal and folderview screenlets work fine.
> >
> > If workspaces aren't supposed to be working, do you know why the webframe
> > screenlet gets reset? Is it something to do with GTK or Compiz, or the
> > screenlet itself? Just wondering if I can hack it.
> >
> > Thanks, if you took the time to read it. I love what you're trying to do
> >
> > --
> > You received this question notification because you are a member of
> > Screenlets Dev Team, which is an answer contact for Screenlets.
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~screenlets-dev
> > Post to : <email address hidden>
> > Unsubscribe : https://launchpad.net/~screenlets-dev
> > More help : https://help.launchpad.net/ListHelp
> >
>
> --
> You received this question notification because you are a member of
> Screenlets Dev Team, which is an answer contact for Screenlets.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~screenlets-dev
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~screenlets-dev
> More help : https://help.launchpad.net/ListHelp
>

Revision history for this message
Robert Withers (baneofbelligerence) said :
#3

The coordinates in the .ini files are reset every time, I guess since in the screenlet code it only checks for x and y values going past the screen boundaries when they've been initialized already. Just to clarify, they work fine when launched after startup, it's just a matter of convenience.

I was using 0.1.6, installed 0.1.7 and still no luck. There's no more Unity 2D in 12.10 (that I could find) but I tried Gnome, Gnome-classic and Cinnamon 2D and none of them had any luck.

I'm going to switch to the dark side and use KDE anyway (not because of the widgets, just wanted to make the change). Sorry to waste your time, but it's a good project and ubuntu really should expand and integrate it.

Thanks, Robert