Re: Mosue double click interval
On Wed, 3 Sep 2003, Ping Cheng wrote: Date: Wed, 3 Sep 2003 17:31:21 -0700 From: Ping Cheng [EMAIL PROTECTED] To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Content-Type: multipart/alternative; boundary=_=_NextPart_001_01C3727B.DD496728 Subject: Mosue double click interval Is there a call to get/set the mouse double click interval? The concept of double, triple, etc. clicks is outside the scope of the X server. The X server just provides mouse click/release events basically. It's entirely up to an application or intermediate windowing toolkit wether or not there is a concept of double clicking the mouse. You need to consult the documentation for the toolkit you're using, ie: GTK+/Qt/etc. -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 over Firewire !
RFC 872. Juliusz ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: X for a cramped PC environment
HS So I'm wondering if: HS 1. anyone has been experimenting with X that's almost so tiny as HS tinyX, and liked what they got? TinyX is full X11, so your question really doesn't make sense. HS 2. kdrive is an easier option instead of a patch kit in newer code HS than 4.2.1? Eh? HS 4. anyone knows a truetype/scalable cursor font? XFree86 includes a Type 1 version of the cursor font. You could use pfaedit to make a TTF version. In XFree86 4.3, the TTF rasteriser also does Type 1 by default. In 4.4, it will also do BDF and PCF. Juliusz ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Confirmation Request (was: XXXSPAMXXX Re: Re: My details)
Read below for instructions on getting your message past my spam pit. Your message with the subject: XXXSPAMXXX Re: Re: My details has been marked as spam by our spam filter. Unfortunately, we get an average of over a thousand spams per day per person at tummy.com. In order to allow us to quickly respond to our clients problems, we have had to set up automated spam processing. In most cases, this does not require any work from our users. In some rare cases, a legitimate e-mail does get caught by our system. This has happened to your message above. You may request that our system complete delivery of this message by send an empty message to: [EMAIL PROTECTED] Please accept my appologies that you have had to go through this extra step. I have my spam filter configured so that most legitimate e-mail comes through without requiring confirmation. Once in a great while, however, it mis-classifies mail (usually when someone is forwarding a piece of spam). If you did not send an e-mail to me with the above subject, it may have due to a spammer forging your e-mail address in an attempt to get an email through to me. See the headers below for more information on the message that generated this response. === Original headers follow === Received: from localhost [127.0.0.1] by secure.tummy.com with SpamAssassin (2.60-cvs 1.195-2003-06-30-exp); Thu, 04 Sep 2003 09:50:18 -0600 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: XXXSPAMXXX Re: Re: My details Date: Thu, 4 Sep 2003 21:19:48 +0530 X-Spam-Level: * MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=--=_3F575F3A.E82EDEA4 ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: DRI and Silicon Motion
Cheshire Cat Fish wrote: Mesa support/conformance is a requirement. The resulting SMI drivers would remain open source, and part of the Xfree/DRI/Linux distribution. That is the plan at least. That's good news. :) There are way too many variables to be able to accurately answer that question (see my answer to your first question). :) But it sounds like at best I can only re-use the very lowest level of drawing code (the part that talks to the hardware_ from the Windows 2000 driver. Everything above that will be different. That's a fair assessment. This is starting to sound like a couple of months work. At least. I don't know how much time per week you're planning to put into this, but, working full time, it would probably take a month or so for someone familiar with DRI internals to get something working using existing driver code good documentation. To get it working *well* would require more time. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: DRI and Silicon Motion
On Thu, 04 Sep 2003 09:49:53 -0700, Cheshire Cat Fish wrote: Licensing issues are not a problem. SMI has approached me asking for this to be done, so I will have full access to all their source code to use to complete this task. I would caution that your conclusion (licensing is not a problem) does not necessarily follow from your premise (SMI asked for it). When I did the Savage driver under contract to S3, I made sure that my contract specifically noted that the resulting code would be submitted to XFree86.org for open source release. That way, there was no crisis of expectations later on. I have also had some clients ask for custom modifications that they did NOT want sent back to XFree86. You just need to be sure of what they want. -- - Tim Roberts, [EMAIL PROTECTED] Providenza Boekelheide, Inc. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: DRI and Silicon Motion
TR I would caution that your conclusion (licensing is not a problem) does not necessarily follow from your premise (SMI asked for it). Just so. Unless otherwise specified, cat_fish's code would be considered a work for hire, and copyright would belong to the employer. = -- Craig Groeschel ladder91 at yahoo dot com AT '00 Tread lightly. Leave no trace. Never forget. Fuel is a resource; people aren't. Dennis Bakke When replying, please do not quote my entire message. __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
