Re: [9fans] rio's New and Resize commands

Re: [9fans] rio's New and Resize commands

[Russ Cox]

what kind of vga controller do you have
on the crashing thinkpads?

Re: [9fans] rio's New and Resize commands

[andrey mirtchovski]

> what kind of vga controller do you have
> on the crashing thinkpads?

neomagic on the ones that do crash...  the simple graphics program
(bouncing lines) that uses lots of allocimage/freeimage tended to
crash them too...  in both accelerated and non-accelerated mode...

in accelerated 1024x768x24 mode i can't open a window bigger than
500x500 pixels.  it simply hangs.

note: i'm not whining and am already accustomed to running in low
bpp's for the sake of speed and stability.  the rio hack deals with
(what i found to be) a mild irritation and possibly an interface
consistency issue :)

note2: i'd rather be running rio in 800x600x8 mode than any X anytime :)
:)

Re: [9fans] rio's New and Resize commands

[andrey mirtchovski]

all our nvidia cards (tnt2, geforce2/3) experience problems with
hardware acceleration.  my tnt2 simply reboots the machine when
aux/vga initializes it, the geforces are displaying at the rate of one
letter every few seconds ('session...  post...'  takes around a minute
from the 's' to the last dot)...  the good thing is, they're fast
enough in unaccelerated mode to use, with the exception being the
New/Resize problem...

also, when hwaccel is on on the thinkpads they tend to crash alot when
using > 8bpp (a normal window resize to a full screen 1024x768 crashed
midway through the sweep).  i think the problem is in allocimage but i
have not investigated further.


andrey

Re: [9fans] rio's New and Resize commands

[Russ Cox]

have you commented out the

	echo hwaccel off >'#v/vgactl'

in /rc/bin/termrc?

that will speed things up quite a bit.

[9fans] rio's New and Resize commands

[andrey mirtchovski]

hi,

in my normal day-to-day interaction with rio i tend to follow along
the lines of most users -- several pretty much stationary windows
(stats, faces, acme and vncviewer) tthat do common tasks and lots of
short-lived terminal windows to interact with other cpu servers,
test code and stuff like that...

since i moved to a bigger screen and higher resolution (1600x1200x32)
i found that creating a new window is a bit of a pain in the butt --
while sweeping with the mouse after selecting 'New' from the menu i
found myself waiting for the opaque window to resize to the new size
stepping through several intermediate resizes.  same with the 'Resize'
command..  (note that this is not a significant problem in smaller
pixel sizes -- allocimage/freeimage copes well on my TNT2, problem is
noticeable at 16/32bpp only)...

furthermore, i thought this to be a bit inconsistent with the
transparent resize of windows when their border has been selected with
mouse button 1...

anyway, long story short, here's a diff that allows me to do
transparent (border only visible) window creation and resize...

this speeds up things a lot.  i'm not sure how it scales on the
'pleasing to the eye' factor though...

andrey

ps: some funny comments are to be found in rio.c too, for those
interested :)

-----------------diff-----------------
p9% diff rio.c rio.c.orig
762c762
< 	Rectangle r, or;
---
> 	Rectangle r;
764a765
> 	i = nil;
773,774c774
< 	or = r;
< 	drawgetrect(or, 1);
---
> 	oi = nil;
783,785c783,788
< 				drawgetrect(or, 0);
< 				drawgetrect(r, 1);
< 				or = r;
---
> 				i = allocwindow(wscreen, r, Refnone, 0xEEEEEEFF); /* grey */
> 				freeimage(oi);
> 				if(i == nil)
> 					goto Rescue;
> 				oi = i;
> 				border(i, r, Selborder, red, ZP);
790,796d792
< 	drawgetrect(or, 0);
< 	i = allocwindow(wscreen, or, Refnone, 0xEEEEEEFF); /* grey */
< 	if(i == nil)
< 		goto Rescue;
< 	border(i, r, Selborder, red, ZP);
< 	flushimage(display, 1);
<