From: Ketil Froyn <ketilf@ifi.uio.no>
  To  : ggi-develop@eskimo.com
  Date: Sat, 3 Jul 1999 14:11:10 +0200 (MET DST)

Re: tile target?

On Sat, 3 Jul 1999, Marcus Sundberg wrote:

> ggix :0 -modes "[GT_16BIT]" -targets
> "tile:0,0,1152,864,(fbdev):1152,0,800,600,(glide)"
> will do what you want.

This gave me:
LibGGI: Checking GGI_INPUT_TILE_3 : (nil)
LibGGI: Checking GGI_INPUT_TILE : (nil)
LibGGI: Checking GGI_INPUT : (nil)
LibGGI: ggiParseMode(0xbffff3fc, 0x81c6364) called
LibGGI: ggiCheckMode(0x81c8708, 0x81c6364) called
LibGGI: display-fbdev: checkmode 1152x864#0x0F1[0x2001010]
LibGGI: display-fbdev: result 0 1152x864#1152x864F1[0x2001010]
LibGGI: res2glideres: breaking on highfreq
display-tile: ggiCheckMode() on visual #1 error -- please explicitly
specify cor
rect mode instead.

Fatal server error:
XGGI doesn't support 0 bpp screens.

> No emulated target will ever support DirectBuffer and acceleration
> at the same time, simply because it is not possible do do this.

Damn :) Can you make XGGI work without DirectBuffering, then? :)

> > Also, there's still the problem of dragging a window from one screen to
> > the other. When I try, the window pops up on the other side of the
> > original screen instead of on the other screen. Is this only possible with
> > the tile-target also?
> The tile target is only one screen so you can drag windows wherever
> you like on that.

But without tile the windows have to stay on one screen?

> > Lastly, I was wondering if I can set interlaced modes on the Voodoo2.
> No. Why would you want to do that?

Cos I have a lousy screen.

Ketil Froyn
--
The angle of the dangle is proportional to the heat of the meat.

http://www.ifi.uio.no/~ketilf/       
mailto:ketilf@ifi.uio.no