On 28 Sep 2005 23:39:51 -0700, Zack Brown wrote: > > On Thu, Sep 29, 2005 at 06:17:19AM +0200, Viktor Griph wrote: > > On Wed, 28 Sep 2005, Zack Brown wrote: > > >On Wed, Sep 28, 2005 at 07:13:52PM +0200, Viktor Griph wrote: > > > > > Yes. Until then you might actually be able to trick FVWM to expand > > variables in the order you want by escaping and use of always true tests. > > > > + I Test (True) GotoDeskAndPage $0 $$[VillageDeskX$0] $$[VillageDeskY$0] > > will probably work for you. That is it will expand the $0 before the Test > > is evalueated, and at the same time change $$ to $, and then expand the > > variables as the test is evalueated and the command executes. > > OK, I've tested this, but it didn't work for me. It had no effect. Does > it actually work for you?
Works for me if you use '$$$$' instead of '$$'. Such additional escaping of dollar is needed, because you are in "+" command. Here is the sample for 2.4.x. In 2.5.12 you may use "Test" instead of "None (*unexisting*)". It should print "12 100 200": SetEnv VillageDeskX3 100 SetEnv VillageDeskY3 200 DestroyFunc TestFunc AddToFunc TestFunc + I None (*unexisting*) Echo $0 $$$$[VillageDeskX$0] $$$$[VillageDeskY$0] TestFunc 3 > Is there some kind of output I could produce that would help debug the > situation? Use command "Echo value" or "Exec xmessage 'value'" if you have xmessage. Regards, Mikhael.
