Grx August 2002

grx@gnu.de

5 participants
13 discussions

new fontdemo.c
by Dimitar Zhekov 29 Aug '02

29 Aug '02

The newest fontdemo with all the patches and: - fix char c -> int c in main() (I'm sure it was int some time ago) - use GR_UNDERLINE_TEXT for underlining (I should RTFM sometimes :-) - dynamically allocate testname (buffer overflow was possible) - allow reverse and underline attributes at startup (-a 1, -a 2) - use 8 bpp modes by default, they're more common that the 4-bit Note: because of the many changes since the last -pre, fontdemo.zip contains a full source (fontdemo.c), not an incrementional patch. E-gards: Jimmy

2 1

Re: grx1 for djgpp 2.x
by Mariano Alvarez Fernandez 29 Aug '02

29 Aug '02

=?iso-8859-1?q?Ben=20Decker?= escribió: > > Hello Mr. Fernandez, > > > > > > For reasons concerning compatibility with older > > > packages, I > > > > was hoping to find a djgpp 2.x compatible package of > > > the > > > > *grx 1.x* sources/binaries. I would prefer building > > > You have two choices: > > > > > > 1- Use the compatibility headers in the GRX 2 "compat" > > > subdirectory, > > > copy grx.h and mousex.h to your include directory and > > > try. I don't know > > > if it suffices. > > > > This doesn't appear sufficient, as there seem to be > > portions of the font structures not supported in the > > compatibility headers. > > > > > 2- Download the orignal 1.03 grx from simtelnet: > > > ftp.simtel.net/pub/simtelnet/gnu/djgpp in the v1tk > > subdir > > > (but I think > > > it only works with DJGPP v1). > > OK, I changed one of the C files so that it doesn't default > to "bad color plane in driver", rather defaults to VGA. But > it was really kind of a kludge. But GRX samples just seem > to freeze... they can't open a window. > > Can you tell me what was done different with the VGA driver > in GRX 2.x that allows me to successfuly open the VGA > screen although I am using Windows 2000? > Not sure, but I think W2000 amd NT catch and permit standard VGA low level programing. > > I am using the library to port the DJGPP V1 X11 library to > DJGPP 2, so it would be good if I could find an answer. Any > info would be appreciated. > Really I don't know grx 1 and djgpp 1, probably is a good idea to post to the djgpp mail list. Regards, M.Alvarez

1 0

grx 1.x sources - grx1 for djgpp 2.x
by Ben Decker 26 Aug '02

26 Aug '02

Hello, For reasons concerning compatibility with older packages, I was hoping to find a djgpp 2.x compatible package of the *grx 1.x* sources/binaries. I would prefer building myself, but ready made binary package is also very welcome. A couple of packages that I am trying to compile call for 'grx.h' and cannot build when upgrading the include to grx20.h Thanks Ben __________________________________________________________________ Gesendet von Yahoo! Mail - http://mail.yahoo.de Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de

2 1

Can't seem to get the colors to work right...
by John R. Evans 23 Aug '02

23 Aug '02

The following program doesn't work: #include <grx20.h> #include <grxkeys.h> #include <stdio.h> int GRXMain( int argc, char **argv ) { int x, y; int maxX, maxY; GrColor color; GrContext *context; GrSetMode( GR_biggest_graphics ); GrSetRGBcolorMode(); GrClearScreen( GrBlack() ); maxX = GrScreenX(); maxY = GrScreenY(); printf("%d %d\n", maxX, maxY ); context = GrCreateContext( maxX, maxY, 0, 0 ); if ( context == 0 ) { printf("Error creating context\n"); exit(0); } GrSetContext( context ); color = GrAllocCell(); for( y=0; y<maxY; y++ ) { for( x=0; x<maxX; x++ ) { GrSetColor( color, x, y, 0 ); GrPlot( x, y, color ); } } GrBitBlt( 0, 0, 0, context, 0, 0 ,maxX, maxY, GrWRITE ); GrDestroyContext( context ); GrFreeColor( color ); GrKeyRead(); return 0; } Please tell me why?

2 1

Re: GRX forward slashes
by Dimitar Zhekov 14 Aug '02

14 Aug '02

>> What concerns me is not the the demo but the raw driver, which has a `basename` in it. >OK, I will apply it. Perhaps a better way is to make a _GrBasename function, easy to move it >out of the raw driver if we need it in other places someday. Perhaps we can use it even now to remove the loadfont.c's: while((chr = *name++) != '\0') { ... } and use: f = doit(name,"",cvt,w,h,minc,maxc); if((f == NULL) && name == _GrBasename(name)) { The main reason for the while() is to cut everything after the first isspace(), which results in failing for any filenames with isspace()-s it them(?!) Even the MS-DOS 8.3 file/directory names are allowed to contain spaces. E-gards: Jimmy

1 0

Re: Font drivers cleanup
by Dimitar Zhekov 14 Aug '02

14 Aug '02

>> Cleanup the font driver a successful font load. >I agree. I was puzzled why the need to left the file open, but the cleanup into the >fileopen driver function doesn't hurt, so I propose apply only the loadfont.c change, >and we doesn't break a posible user program that rely in this 'feature' of the font At first I also patched loadfont.c only, but if some user program relies on this 'feature' (I wonder how - obtain a driver pointer and then access it's symbols directly?) , it's exactly the loadfont change that will break it. After loading a font, all the driver functionality can be used via the respective high-level GRX functions, so I prefer removing openfile cleanups. The choice is yours, of course, you are the maintainer, and you're right that leaving them won't hurt. E-gards: Jimmy

1 0

[Fwd: Re: Font drivers cleanup]
by Mariano Alvarez Fernandez 13 Aug '02

13 Aug '02

I forgot to change the 'To' to grx :-) -------- Original Message -------- Asunto: Re: Font drivers cleanup Fecha: Tue, 13 Aug 2002 23:54:36 +0200 De: Mariano Alvarez Fernandez <malfer(a)telefonica.net> A: jimmy(a)is-vn.bg Referencias: <QM71A6521W4B8A861YUA7IFKHA7YUZU.3d58c56b@jimmy> Dimitar Zhekov escribió: > Cleanup the font driver a successful font load. > > By default, a font driver is cleaned up either after an unsuccessful > font load or on the next attempt to load a font with this driver; > any > open files or allocated memory are cleaned when exiting the program, > but I'm not sure about the X11 and Windows resources. Anyway, alwaus > cleaning up after a font load seems more proper to me than to wait > for > the next load or rely on the C library cleanup at exit. > > I tracked down the calls to the driver functions and tested the > patch > with GrLoadFont() and GrBuildConvertedFont(). It seems to work, and > the input font file can now be open for writing, unlinked and so on, > but more testing is required. > I agree. I was puzzled why the need to left the file open, but the cleanup into the fileopen driver function doesn't hurt, so I propose apply only the loadfont.c change, and we doesn't break a posible user program that rely in this 'feature' of the font drivers. Ok? Regards, M.Alvarez

1 0

Font drivers cleanup
by Dimitar Zhekov 13 Aug '02

13 Aug '02

Cleanup the font driver a successful font load. By default, a font driver is cleaned up either after an unsuccessful font load or on the next attempt to load a font with this driver; any open files or allocated memory are cleaned when exiting the program, but I'm not sure about the X11 and Windows resources. Anyway, alwaus cleaning up after a font load seems more proper to me than to wait for the next load or rely on the C library cleanup at exit. I tracked down the calls to the driver functions and tested the patch with GrLoadFont() and GrBuildConvertedFont(). It seems to work, and the input font file can now be open for writing, unlinked and so on, but more testing is required. E-gards: Jimmy

1 0

More user mode stuff
by Dimitar Zhekov 08 Aug '02

08 Aug '02

What is so special about modetest so it requires 4755? With the in- out-port (s)vga drivers disabled, it runs OK with build.users 0755. The BGI examples need no 4755 either, looks like you've missed 'em.

1 0

fontdemo update
by Dimitar Zhekov 07 Aug '02

07 Aug '02

- do not precede the error messages with the program name - deltay support, as in some X11 libraries (separate <=> deltax) - display the cyrillic quick-fox only if character range has 192..255 - GRX uses slashes internally to represent font paths. For example, the RAW driver does not check for backslashes when taking basename, but works even under plain DOS, and so does fontdemo with ../fonts.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

Grx August 2002