hey! the "sleep 10" thing worked! thanks! :)
C
On Sat, 30 Sep 2000, Mikhael Goikhman wrote:
> On 29 Sep 2000 11:24:00 -0800, Czarina Caro L. Tablante 1995-24644 wrote:
> >
> > > I looked at sxpm in the xpm package version 3.4j.
> > >
> > > sxpm.c reads the geometry argument, but doesn't set x/y coordinates.
> > > The problem with geometry is in sxpm, not fvwm.
> > > It might not be hard to fix sxpm.
> > >
> > > If you mention the version of fvwm you are using, it might be possible
> > > to make fvwm move the window to the location you want after its
> > > created.
> >
> > sxpm -geometry +22+0 /home/czarina/pet.xpm &
> >
> > when i restart XWindows, the sxpms are in their correct positions
> > already, but never on startup.
>
> Like Dan said, sxpm does not set any position hints, so fvwm can know
> nothing about your +22+0. The bug is in sxpm.
>
> Here is what happens. sxpm does not itself manage -g (-geometry) argument.
> I suppose it is done in XtInitialize(), because there is no other places
> in the source where it can be managed.
>
> When sxmp is run under fvwm (or other wm with own placement policy), fvwm
> places it accordingly to your *Placement style options, since there are no
> any program or user position hints. Can be verified with 'xwininfo -size'.
>
> But when sxpm is run outside of wm (or before it), the -geometry flag
> *is* applied. Add 'sleep 10' without ampersand to work around sxpm bug.
> Without (or with small) sleep, it is not guaranteed that sxpm will be
> mapped before fvwm is run, so you can get random results, like you did.
>
> Regards,
> Mikhael.
>
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Mon Oct 02 2000 - 07:30:39 BST