Re: Multi-head HOWTO
Andreas Beck writes:
I'm just pondering the thought, if we should add that functionality to
LibWMH, as it is designed to do the windowing-related stuff, but on the
other hand it doesn't quite seem to be the right place ...
I think doing it with LibWMH is the best place for it ("grabbing" the
mouse is a very windowing-system-ish concept).
Cheers,
__
\/ Andrew Apted [EMAIL PROTECTED]
Re: Multiple windows??
On Sat, 19 Feb 2000, Andreas Beck wrote: What you need is LibGWT and LibWMH. Unfortunetly, both are quite unusable. Huh ? LibGWT doesn't work AFAIK, That is, what I said. but LibWMH works perfectly for me. OK - the demo of LibWMH works (in an earlier cvs-snapshot), but AFAIK it's still at pre-alpha-state... Where do you have problems ? LibWMH doesn't compile. Look: gcc -DHAVE_CONFIG_H -I. -I. -I.. -DBUILDING_LIBGGIWMH -I../include -g -O2 -D_REENTRANT -D_THREAD_SAFE -g -Wall -Wstrict-prototypes -Wp,-MD,.deps/init.pp -c -fPIC -DPIC init.c -o init.lo init.c:40: `GGIWMHCONFFILE' undeclared here (not in a function) init.c:41: `GGIWMHTAGLEN' undeclared here (not in a function) init.c:41: initializer element is not constant make[2]: *** [init.lo] Error 1 make[2]: Leaving directory `/home/programmer/ggi/degas/lib/libwmh/ggiwmh' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/programmer/ggi/degas/lib/libwmh' make: *** [all-recursive-am] Error 2 Christoph Egger E-Mail: [EMAIL PROTECTED]
Re: Two simple questions
On Tue, Feb 15, 2000 at 06:40:42PM +0100, Marcus Sundberg wrote: I still trying to get my head around all this stuff. Two simple questions: KGIcon makes KGI drivers look like fbdev drivers, right ? Now, if I run a GGI program on a fbdev console, does it think it's just running on a fbdev device, or does it realise all the KGI stuff is hidden behind there, and use all that as well ? LibGGI detects KGIcon drivers, and is currently able to make use of generic acceleration though ioctl()s. The other thing is that the i740 code I'm converting from XFree has a few parameters that allow overriding autodetected stuff, and so on. I don't want to throw away functionality, so how are parameters passed into the driver ? I can't see where this happens in the code. Currently, you simply must use the regular Linux kernel MODULE_PARM() macro to pass driver-specific parameters. This helps a lot to clarify things - thanks. -- Jim Peters / __ | \ Aguazul / /| /| )| /| / )|| \ jim@aguazul. \ (_|(_|(_|(_| )(_|I /www.aguazul. demon.co.uk \._) _/ / demon.co.uk
Re: targets and ?sources?
On Fri, Feb 18, 2000 at 11:07:04AM -0500, Brian S. Julin wrote: For GBL and OVL to work nicely, we will need some way of allocating offscreen video memory. Any ideas on that ? Should that go into LibGGI or should we push it into an extension ? If it's going to play nice with SetMode, it'll have to go in the base. Else, we have a new AdvancedSetMode and any app using the extension is barred from calling vanilla SetMode. That's the only issue I see with extension vs core. Good question. I was wondering about this - about which part of the code is in charge of allocating video memory. Is it the chipset driver, or KGI(con) ? There is an issue here when different areas of memory have different capabilities, for example on i740, the hardware-cursor buffer (if used) must be in the first 4Mb. Jim -- Jim Peters / __ | \ Aguazul / /| /| )| /| / )|| \ jim@aguazul. \ (_|(_|(_|(_| )(_|I /www.aguazul. demon.co.uk \._) _/ / demon.co.uk
Re: targets and ?sources?
On Sun, 20 Feb 2000, Jim Peters wrote: Good question. I was wondering about this - about which part of the code is in charge of allocating video memory. Is it the chipset driver, or KGI(con) ? The "chipset driver" == KGI(con). The allocation would be handled by a combination of the driver and the driver-lib. It's sort of a two way street -- offloading the functionality into userspace and just having the driver check the requests for security has the benefit of keeping the kernel drivers simple, but implementing a standard API in-kernel would help reduce the number of customized driver libs needed. There's been a lot of correspondence on a generic "feature" API (see the list archives.) It would handle all types of features and would integrate in some way with the mode parameters to allow the negotiation of features vs each other and vs the video mode. Probably what needs to be done is pick one feature that people need the most and implement it in the form of the feature negotiation API -- but with the back-end being a simple hack because even though the API is generic, only one feature has been implemented, then work on making it handle more than one type of feature. BTW, we should accumulate all the old list traffic about this in one file and post it on the website for easy access because this thread comes up so often. -- Brian
Re: Multiple windows??
but LibWMH works perfectly for me. Where do you have problems ? LibWMH doesn't compile. Look: Huh ? Please make clean, ./configure and retry. It _does_ compile for me. I just checked. If that doesn't do the trick, there might be an issue with autoconf and friends. Marcus - you're the autoconf expert - could you check that out ? Also tell me, when you have implemented the "GrabMouse" control command, so that I can add an appropriate function in LibWMH to make use of it. CU, ANdy -- = Andreas Beck| Email : [EMAIL PROTECTED] =
