Grx June 2004

grx@gnu.de

3 participants
3 discussions

Patch: W32 event handling
by Peter Gerwinski 19 Jun '04

19 Jun '04

Hello everyone, I hacked some more event handling into the W32 version of GRX: - GR_SIZE_CHANGED: Tell the program that the size of the GRX window was changed from outside - GR_OS_DRAW_REQUEST: Let the program know that the OS wants the program to redraw its window. (Normally, GRX handles this in the background, but if you use non-GRX output such as OpenGL in parallel, this can be useful.) - GR_COMMAND: Events that come from, e.g., a menu rather than the keyboard or mouse directly Patch attached. Have fun, Peter -- (_G-N-U_) Dr. rer. nat. Peter Gerwinski <peter.gerwinski(a)g-n-u.de> o o Geschäftsführer und Software-Entwickler G-N-U GmbH, EDV-Dienstleistungen, http://www.g-n-u.de

1 0

Problem with Multi Monitor Setup
by anon permutation 16 Jun '04

16 Jun '04

Hi, I have a computer that has multiple CL-GD5429 graphics cards. Each graphics card has 2MB memory on it, and each card supports 4 monitors. Therefore, if I have 2 cards, I can support up to 8 different monitors. The OS is DOS 6.22. To control which monitor to draw on, I simply outportb(0x210, x) , where x is the monitor's number. My program is running with driver string = "VESA 640 480 256" and mode is 640 480 @ 8bpp. For my test program, I simple show a banner at diffenert places on different monitors. The program runs fine at the beginning, but after about 5-7 mins, it behaves strangely. For example, when I placed a banner at 0,50 of the screen, it would show up at maybe 75, 80 of the screen. It always show up at the right monitor, but the location is wrong. What is causing this problem? Is it because GRX got confused by the multi monitor setup and therefore draws on the wrong part of video memory? What can I do to fix this? Please help. Thanks. _________________________________________________________________ MSN 9 Dial-up Internet Access fights spam and pop-ups now 3 months FREE! http://join.msn.click-url.com/go/onm00200361ave/direct/01/

1 0

Simplifying cross-development
by Peter Gerwinski 12 Jun '04

12 Jun '04

Hi, cross-development with GRX has always required some manual hacking: You have to adjust compiler, linker, etc. manually, and when you try to use, for instance, makefile.dj2 under GNU/Linux, `make clean' fails because the shell does not like `if exist foo.o del foo.o'. The attached `diff' patches the configure script and the makefiles such that all this works automatically. :-) If you do not cross-compile, you should not notice the difference, but, as I do not have a self-hosting DJGPP or MINGW intalled, I did not test this. How this works: - The target directory is now named INSTALLDIR for all platforms. (This makes it much easier and less error-prone to configure it automatically.) - There is a new variable CROSS_PLATFORM which contains the prefix for the cross development tools (e.g. "i386-mingw32-" when you want to use i386-mingw32-gcc instead of plain gcc). - There is a new variable HAVE_UNIX_TOOLS. When set to "y", the DJ2 and W32 makefiles use "rm" instead of "del", "cp" instead of "copy", etc. This is needed for cross-development, but it is also useful if you are working with a self-hosting DJGPP or mingw32. - You can edit all this in makedefs.grx. In addition, the configure script has been adapted to set these variables automatically if you feed it with a GCC-style target specification such as "--target=i386-pc-msdosdjgpp". Have fun, Peter

2 2

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 June 2004