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: Multi-head HOWTO
Joseph Carter [EMAIL PROTECTED] writes: That's fine, and a good default. If the application wants to grab the mouse, it should request to do so specifically.. The point is - why whould an application designed to run fullscreen (which all LibGGI apps are by definition) ever want to "grab the mouse" ? I think there ought to be a method for the application to grab the mouse. QuakeForge has a method for this under its option menu which isn't present for the GGI target. However I'm considering adding functionality to do this. Mainly because no Quakeforge target should be better than the GGI one. ;-) The idea is that we do it with *SendEvent() and GII_CMDCODE_PREFER_RELCOORD and GII_CMDCODE_PREFER_ABSCOORD, and thus make it a quite useful functionality for non-games also. This way we also doesn't add a single byte of code to inputs that don't have functionality to do this. What do you think Andy? Sounds good? //Marcus -- ---+ Marcus Sundberg| http://www.stacken.kth.se/~mackan Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: [EMAIL PROTECTED]
Re: Multi-head HOWTO
On Fri, Feb 18, 2000 at 10:48:50PM +0100, Marcus Sundberg wrote: That's fine, and a good default. If the application wants to grab the mouse, it should request to do so specifically.. The point is - why whould an application designed to run fullscreen (which all LibGGI apps are by definition) ever want to "grab the mouse" ? Think fbdev... I think there ought to be a method for the application to grab the mouse. QuakeForge has a method for this under its option menu which isn't present for the GGI target. However I'm considering adding functionality to do this. Mainly because no Quakeforge target should be better than the GGI one. ;-) I will admit, before Mercury broke the input code for every target, -ggi was my standard "I have no idea if this is gonna work or not" testbed, mostly because it's the most likely to actually work first, and second it's the most likely not to hose my box if it doesn't. = I think GII is useful even in places where GGI isn't, personally. -- Joseph Carter [EMAIL PROTECTED] Debian Linux developer http://tank.debian.net GnuPG key pub 1024D/DCF9DAB3 sub 2048g/3F9C2A43 http://www.debian.org20F6 2261 F185 7A3E 79FC 44F9 8FF7 D7A3 DCF9 DAB3 rcw dark: caldera? Knghtbrd rcw - that's not a distribution, it's a curse rcw Knghtbrd: it's a cursed distribution
Re: Multi-head HOWTO
I think there ought to be a method for the application to grab the mouse. QuakeForge has a method for this under its option menu which isn't present for the GGI target. However I'm considering adding functionality to do this. Mainly because no Quakeforge target should be better than the GGI one. ;-) ROTFL ... The idea is that we do it with *SendEvent() and GII_CMDCODE_PREFER_RELCOORD and GII_CMDCODE_PREFER_ABSCOORD, and thus make it a quite useful functionality for non-games also. Yes. This way we also doesn't add a single byte of code to inputs that don't have functionality to do this. What do you think Andy? Sounds good? Yeah ... Definitely. 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 ... However it would have the advantage of knowing what target it is running on (as it is an extension) and thus be able to only send the codes when the functionality is available and give nice error codes, if not. This way we could keep the call a private feature of the X input libs (i.e. we don't need to alloc from the public command numberspace). While someone does that, he might as well want to introduce a method to define the cursor shape of the window system in use. That would be very handy for a GUI toolkit, as you could then avoid the use of soft cursors when running on a window system. Marcus: Just decide what you like better. Both implementation possibilities (straight away as commands for direct application use or via LibWMH) seem o.k., so just do the one you like better. CU, ANdy -- = Andreas Beck| Email : [EMAIL PROTECTED] =
Re: Multi-head HOWTO
On Thu, Feb 17, 2000 at 10:51:59PM +, Firstname Lastname wrote: GGI_DISPLAY='tile:0,0,640,480,(fbdev:/dev/fb0):640,0,640,480,(fbdev:/dev/fb1)' quake-ggi This is, of course, assuming you're using QuakeForge's stable release... Question: When i put 2 monitors next to each other, they get horizontal black stripes running up and down the screens when they are bolth powered on. If i power one of them off, everything is fine on the other one. what gives? Answer: The magnetic fields generated by the monitors are interfering with each other. I reduced this interference to a tolerable level by placing my middle monitor into a "monitor box", a box which is designed to magnetically shield a monitor. Now all three monitors are at tolerable levels. If you want one of these you can order them from DLS Electronics @ 847-537-6400. However be warned, they cost $990 for a 14 inch monitor and $1140 for up to a 20 inch monitor because they use exotic metals. On the plus side, you can probably get away with having just one carefully placed box, for up to 3 monitors, and they give you a neat bookshelf above your monitor :) Note that any 4-sided or so (top, sides, back) hood for a monitor lined with anything grounded oughtta do the trick. And it'll cost you several hundred less! Be wary of cooling needs. Question: My mouse doesn't work in quake-ggi! Answer: Neither does mine. I haven't put much effort into finding out why, since i use the keyboard. This is a "feature" of the GGI target... ctrl-alt-M will grab the mouse and the same keypresses will release it. I consider this behavior to be brain-damaged and otherwise generally not terribly good thinking, but I don't know enough GGI to be able to change it (or even whether or not it CAN be changed!) You play with just the keyboard? *chortle* You must not do multiplayer. -- Joseph Carter [EMAIL PROTECTED] Debian Linux developer http://tank.debian.net GnuPG key pub 1024D/DCF9DAB3 sub 2048g/3F9C2A43 http://www.debian.org20F6 2261 F185 7A3E 79FC 44F9 8FF7 D7A3 DCF9 DAB3 I sat laughing snidely into my notebook until they showed me a PC running Linux. And oh! It was as though the heavens opened and God handed down a client-side OS so beautiful, so graceful, and so elegant that a million Microsoft developers couldn't have invented it even if they had a hundred years and a thousand crates of Jolt cola. -- LAN Times
