Hmm, looking back at this problem, it seems that workspace switching actually works when *not* trying to maximize too. So the following works:

 <flurb name="Evolution">
    <matchers>
      <matcher name="DevilsPieMatcherWindowName">
        <property name="window_title" value="^Evolution.*"/>
      </matcher>
    </matchers>
    <actions>
<!--     <action name="DevilsPieActionResize">
        <property name="maximized" value="TRUE"/>
      </action>-->
      <action name="DevilsPieActionSetWorkspace">
        <property name="workspace_index" value="2"/>
      </action>
      <action name="DevilsPieActionDebug"/>
    </actions>
  </flurb>

and then evolution itself remembers maximization state, so all is fine for me. Maybe this is a bug in the maximization code instead?

/Mikael

Ross Burton wrote:
On Fri, 2004-11-19 at 23:58 +0100, Mikael Nilsson wrote:

But suddenly after today's upgrade to GNOME 2.8 (I think, it was a
while since I restarted Evolution....), Evolution stays on the
workspace where I start it.

Similar flurbs still work for openoffice, mozilla, ...

I get this at the console when running devilspie manually:

(devilspie:31318): Wnck-WARNING **: Received a timestamp of 0; window
activation may not function properly.


This appears to be GNOME's new window placement magic, which puts
applications on the workspaces they were started on (not the current
workspace when they are mapped__.

I'll probably have to work around this some way...

Ross

-- Plus ça change, plus c'est la même chose
begin:vcard
fn:Mikael Nilsson
n:Nilsson;Mikael
org:Royal Institute of technology;KMR group, NADA
adr;dom:;;;Stockholm
email;internet:[EMAIL PROTECTED]
tel;work:+46 8 7906896
x-mozilla-html:FALSE
url:http://kmr.nada.kth.se
version:2.1
end:vcard

Reply via email to