Grx

grx@gnu.de

559 discussions

Re: GRX and GNU
by Hartmut Schirmer 24 Apr '00

24 Apr '00

On Sat, 22 Apr 2000, Richard Stallman wrote: >Are you the chief maintainer of GRX? And should we >consider it a package of GNU software? Well. I didnŽt really maintain GRX for about 2 years now. Since no one did active and public maintance since then, I might still be what you call the Žchief maintainerŽ, but I wonŽt do major active maintaince now or in future. (I promised Peter Gerwinski to integrate the BCC2GRX compatibility lib for Borland graphics interface API [BGI]) There were several requests on the GRX mailing list for this vacancy but ... I read through my GRX email archive this easter and noticed 2 or 3 people I could directly ask to take over maintance. WeŽll see. >Here's an explanation of what it means for a program >to be GNU software: > >====================================================================== >Calling a program GNU software means that its developers and the GNU >project agree that "This program is part of the GNU project, released >under the aegis of GNU"--and say so in the program. GRX definitly needs some bug fixes, changing the source and the docs to include this message should be quite easy >This means that we normally put the program on ftp.gnu.org (although >we could instead refer to the developer's choice of ftp site) and that >we put the official pages describing the program on the GNU web >server. (It is ok to have more informal pages about secondary issues, >such as discussion meant for people who want to help develop the >package, on some other site.) ItŽs know on WWW (www.gnu.de/grx) and on the simtel ftp server (DJGPP package). Moving it to an offical GNU ftp server would require some work on configuration, see below. >It means that the developers agree to pay some attention to making the >program work well with the rest of the GNU system--and conversely that >the GNU project will encourage other GNU maintainers to pay some >attention to making their programs fit in well with it. > >Just what it means to make programs work well together is mainly a >practical matter that depends on what the program does. But there are >a few general principles. Certain parts of the GNU coding standards >directly affect the consistency of the whole system. These include >the standards for configuring and building a program, and the >standards for command-line options. It is important to make all GNU >programs follow these standards, where they are applicable. autoconf support is currently missing. >A GNU program should not recommend use of any non-free program, and it >should not refer the user to any non-free documentation for free >software. The need for free documentation to go with free software is >now a major focus of the GNU project; to show that we are serious >about the need for free documentation, we must not contradict our >position by recommending use of documentation that isn't free. > >Occasionally there are issues of terminology which are important for >the success of the GNU project as a whole. So we ask maintainers of >GNU programs to follow them. For example, the documentation files >and comments in the program should speak of Linux-based GNU systems or >GNU/Linux systems, rather than calling the whole system "Linux", and >should use the term "free software" rather than "open source". documentation for the GRX graphics library currently ist outdated (still v1.x doc), needs some work to add doc to the source that can be converted by something like doxygen (is it free?) >Deciding that a program is GNU software does not necessarily require >transferring copyright to the FSF; that is a separate question. If >you transfer the copyright to the FSF, the FSF will enforce the GPL >for the program if someone violates it; if you keep the copyright, >enforcement will be up to you. Nearly all contributed agreed on assigning GRX to the FSF. Sadly I didnŽt manage to contact Ulrich Leodolter. Ulrich did the X11 port :( IŽll try again next rainy day ... Summary: - GRX isnŽt ready to be called GNU software (autoconf & docs missing) - GRX isnŽt activley maintained - GRX including the X11 dricer copyright canŽt be assigned to FSF, GRX without the X11 driver canŽt be called GNU software

1 0

Problems with GrCursor
by Josu Onandia 23 Apr '00

23 Apr '00

Hi all, I've been having problems with the GrDisplayCursor function. In my case, sometimes the cursor is drawn partially. I think I've found the error in GrDisplayCursor. If the cursor is 8 pixels wide, the work area is 16 pixels wide. Let's supose a call to GrDisplayCursor with C->xcord = 323: C->xcord = 323; C->xoffs = 0; C->xsize = 8; C->xwork = 16; ----------------------- call GrDisplayCursor xpos = 323; xsiz = 16; xwrk = 312; ... (save bitmap from 312 to 327) [our cursor goes from 323 to 330] ... xpos = 11; xsiz = 8; if(xsiz > (C->xwork - xpos)) xsiz = C->xwork - xpos; ====> xsiz = 5; (draw a cursor 5 pixels wide) IMHO this is a bug. I think GrDisplayCursor tries to place the cursor in the middle of the work area, but in a coordinate multiple of 8: xwrk = (xpos - (C->xsize >> 1)) & ~7; but sometimes the result lets the cursor partially outside the work area. I think after this line is necesary a correction: if((xpos + C->size) > (xwrk + xsiz)) xwrk += 8; The same applies to vertical coordinates. What do you think about it? Josu Onandia Dpto. I+D Software. e-mail: jonandia(a)fagorautomation.es ---------------------------------------------------- Fagor Automation, S.Coop. Barrio San Andres, s/n - P.O. Box. 144 Mondragon 20500 - SPAIN http://www.fagorautomation.mcc.es

2 1

Test programs launcher
by Mariano Alvarez Fernández 22 Apr '00

22 Apr '00

Hi, I have coded a tiny prog to launch the GRX test programs. It's simple but nice (I think). The actual version only react to mouse and the Escape key, if people like it I can enhance it. I put the program under GPL, but no problem to put it under PD to easily add it to the GRX distribution (really I think example programs must be PD, because they are examples :-). I will be happy if someone try it, you can download sources from: http://teleline.terra.es/personal/malfer/zipfiles/demgrx10.zip Greetings M.Alvarez. P.D. Sorry, for my bad english.

1 0

patch.exe
by DAANEN Vincent 20 Apr '00

20 Apr '00

Can someone tell me where I can find patch.exe for Dos/win32 ?

2 1

Font converter from Truetype or BDF fonts to GRX fonts
by Herbert Reichardt 19 Apr '00

19 Apr '00

I've written a utility to convert Truetype and BDF-Fonts to GRX-Fonts. If you use it together with the program ttf2bdf from http://www.freetype.org you can do a conversion: ttf->bdf->grx fonts. If you need fonts with different sizes, with this solution you get much better looking fonts compared to the internal resizing functions of the grx-lib. The program can be downloaded at: http://home.nahesurf.de/herbert.reichardt/download.htm Maybe this program can be useful for some people who are working with grx. Is anyone working on a windows port of grx-lib ? Bye Herbert

2 1

Re: compiling grx23 with 2.95.2
by Hartmut Schirmer 18 Apr '00

18 Apr '00

On Mon, 17 Apr 2000, Klaus Friis Østergaard wrote: > it leaves with messages about not valid asm set 2 register CREG >> in line 48 of shiftscl.c >> >> can you help me? Hi Klaus, Andris Pavenis posted a patch last August: RE: error in compiling utils/shiftscl.c Datum: Wed, 18 Aug 1999 14:58:49 +0300 Von:pavenis@lanet.lv Hope it works Hartmut *** GRX23/src/include/gcc/memfill.h~4 Mon May 18 11:30:56 1998 --- GRX23/src/include/gcc/memfill.h Wed Aug 18 14:46:56 1999 *************** *** 182,188 **** "9: \n" \ : "=r" ((void *)(p)), "=r" ((int)(b)) \ : "d" ((int)(c)), "0" ((void *)(p)), "1" ((int)(b)) \ ! : "ax", "cx", "dx" \ ); \ } while (0) --- 182,188 ---- "9: \n" \ : "=r" ((void *)(p)), "=r" ((int)(b)) \ : "d" ((int)(c)), "0" ((void *)(p)), "1" ((int)(b)) \ ! : "ax", "cx" \ ); \ } while (0) *** GRX23/src/include/gcc/mempeek.h~4 Mon May 4 20:23:36 1998 --- GRX23/src/include/gcc/mempeek.h Wed Aug 18 14:47:28 1999 *************** *** 88,94 **** " "#INS"b %%ah," SEL "2(%1) \n" \ : /* nothing */ \ : "a" ((unsigned)(C)), "r" ((void *)(P)) \ - : "ax" \ ); \ } while (0) --- 88,93 ---- *** GRX23/src/utils/shiftscl.c~4 Sun Apr 5 22:48:50 1998 --- GRX23/src/utils/shiftscl.c Wed Aug 18 14:40:24 1999 *************** *** 44,50 **** " movb %%ch,(%4) " : "=r" ((void *)s), "=r" ((void *)d), "=r" ((int)w) : "0" ((void *)s), "1" ((void *)d), "2" ((int)w), "c" ((int)shift) ! : "ax", "cx" ); # elif defined(__TURBOC__) asm push ds ; --- 44,50 ---- " movb %%ch,(%4) " : "=r" ((void *)s), "=r" ((void *)d), "=r" ((int)w) : "0" ((void *)s), "1" ((void *)d), "2" ((int)w), "c" ((int)shift) ! : "ax" ); # elif defined(__TURBOC__) asm push ds ; *************** *** 98,104 **** " jne 1b " : "=r" ((void *)s), "=r" ((void *)d), "=r" ((int)w) : "0" ((void *)s), "1" ((void *)d), "2" ((int)w), "c" ((int)shift) ! : "ax", "cx" ); # elif defined(__TURBOC__) asm push ds ; --- 98,104 ---- " jne 1b " : "=r" ((void *)s), "=r" ((void *)d), "=r" ((int)w) : "0" ((void *)s), "1" ((void *)d), "2" ((int)w), "c" ((int)shift) ! : "ax" ); # elif defined(__TURBOC__) asm push ds ;

3 2

compiling grx23 with 2.95.2
by Klaus Friis Østergaard 17 Apr '00

17 Apr '00

> Hi, > > I am trying to compile grx23 with the gnu gcc 2.95.2 compiler it fails. > > I have changed the CC = gcc > to CC = /usr/local/bin/gcc where I have my gcc-2.95.2 compiler along with > GPC > > I want to use GRX along with Gnu Pascal Version 19991030 which requeres > gcc 2.95 > > this is the output when I run 'make -f makefile.lnx' the second time: > make -C src STATIC=1 -f makefile.lnx > make[1]: Entering directory `/usr/src/grx-2.3/src' > /usr/local/bin/gcc -c -O6 -Wall -DLFB_BY_NEAR_POINTER -pipe > -fomit-frame-pointer -I. -I./include -I../include -I../addons/print > utils/shiftscl.c -o utils/shiftscl.o > make[1]: Leaving directory `/usr/src/grx-2.3/src' > > it leaves with messages about not valid asm set 2 register CREG > in line 48 of shiftscl.c > > can you help me? > > > > Klaus F. Østergaard > >

4 3

RE: GrCustomCircleArc
by Josu Onandia 13 Apr '00

13 Apr '00

Hi Hartmut, I'm sorry for the delay, but I've been very busy. I've just applied your patch to the dashedsegment function, and it works just fine. Thank you very much. By the way, the code I sent to you was only a simplification, my real code was: GrSetClipBox(6, 0, 506, 333); GrCustomCircleArc(393,235,137,241,900,GR_ARC_STYLE_OPEN,&linestyle); Josu Onandia > -----Mensaje original----- > De: Hartmut Schirmer [SMTP:hartmut.schirmer@arcormail.de] > Enviado el: jueves 6 de abril de 2000 22:19 > Para: Josu Onandia > CC: grx(a)gnu.de > Asunto: Re: GrCustomCircleArc > > On Wed, 05 Apr 2000, Josu Onandia wrote: > >Hi, > > > >With the following code I get an Access Violation: > > > >unsigned char pattern[2] = { 2, 2}; > >GrLineOption linestyle = { 15, 1, 2, pattern }; > > > >GrCustomLine(-2, 0, 1, 0, &linestyle); > > > >I've followed the execution until the call to 'dashedsegment', but then I > >get a bit lost. > >What is clear is that when this function calls (*doseg), the variables > >'start' and 'end' > >haven´t been initialized. > > Hi Josu, > > looks like you found a bug in one of the most compicated parts of GRX. > > Some years ago I rewrote the intersection function several time until > it worked without overflow / underflow / division by zero / ... in the > usual cases. > > Your example doesn´t look like a usual case but of course should give > an access violation. > > The problem is the while loop doesn´t set start & end but reports actual > state as ´on´ > > This patch should prevent the access violation. I don´t know if it´s the > right soloution for this problem but it doesn´t break the linetest demo: > > Hope it helps, > Hartmut > > *** drwcpoly.c.org Thu Apr 6 21:03:38 2000 > --- drwcpoly.c Thu Apr 6 22:18:11 2000 > *************** > *** 231,237 **** > int x,y,dx,dy; > int error,erradd,errsub,count; > int xinc1,xinc2,yinc1,yinc2; > ! int start[2],end[2]; > > /* find the current starting segment for the pattern */ > pos = (p->ppos %= p->plength); > --- 231,237 ---- > int x,y,dx,dy; > int error,erradd,errsub,count; > int xinc1,xinc2,yinc1,yinc2; > ! int start[2],end[2], se_init; > > /* find the current starting segment for the pattern */ > pos = (p->ppos %= p->plength); > *************** > *** 267,275 **** > --- 267,277 ---- > yinc1 = yinc2; > xinc1 = 0; > } > + se_init = 0; > if(on) { > start[0] = x; > start[1] = y; > + se_init = 1; > } > else { > prev = NULL; > *************** > *** 279,284 **** > --- 281,287 ---- > if(on) { > end[0] = x; > end[1] = y; > + se_init |= 2; > } > if((error -= errsub) < 0) { > error += erradd; > *************** > *** 300,314 **** > if ( !old_state && on && count > 0) { > start[0] = x; > start[1] = y; > } else > if ( old_state && !on) { > (*doseg)(start,end,prev,NULL,p); > prev = NULL; > } > /* else: zero length element(s), continue current segment */ > } > } > ! if(on) (*doseg)(start,end,prev,next,p); > p->on = on; > } > > --- 303,321 ---- > if ( !old_state && on && count > 0) { > start[0] = x; > start[1] = y; > + se_init = 1; > } else > if ( old_state && !on) { > (*doseg)(start,end,prev,NULL,p); > prev = NULL; > + se_init = 0; > } > /* else: zero length element(s), continue current segment */ > } > } > ! if(on && se_init==3) { > ! (*doseg)(start,end,prev,next,p); > ! } > p->on = on; > } > > >

1 0

GRX under linux/X11
by Giovanni MORUZZI 11 Apr '00

11 Apr '00

Hi, I have written several grx programs under linux/X11. I have set GRX20DRV="xwin::privcmap" and, inside the program, I start the graphic mode with GrSetMode(GR_width_height_color_graphics,800,600,256); however, the corresponding window is opened in grx 800x600x64 K mode, i.e., with 16 bpp. This has always been OK with me, till recently I tried to install my programs in an older computer where only 8 bpp is supported, a grx 800x600x256 window is opened there, but the window is black. Is there any way to limit the number of colors to 256 (8 bpp)? Thank you for any help which anyone can give me, Giovanni ----------------------------------------------------------------------- Giovanni Moruzzi Dipartimento di Fisica dell'Universita' di Pisa Via Filippo Buonarroti 2 I-56127 Pisa, Italy Tel. +39/050 844 559 Fax +39/050 844 333 E-mail: giovanni(a)moruzzi1.df.unipi.it or moruzzi(a)mailbox.difi.unipi.it -----------------------------------------------------------------------

1 0

Mouse problem
by richard＠stardate.bc.ca 10 Apr '00

10 Apr '00

I am using grx with DJGPP. I am having a problem in one function. By remming ot sections of code I have isolated the problem down to GrMouseGetEventT( GR_M_EVENT, &rat, 0 ); In Windows 95 I get fairly predictable results but in DOS I lock up, hard enough that ctrl+alt+del does not work, I have to use the reset button. In DOS if I single step through the function (and function calls with in my function) my function works as expected, I guess the debugger is getting in the way. If I erase the mouse pointer with GrMouseEraseCursor(); then, other than having no mouse displayed, my function works as expected from both DOS and Windows. Any ideas? (What did I do/not do?) Cheers Richard

1 0

← Newer
1
...
47
48
49
50
51
52
53
...
56
Older →

Jump to page:

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