xkb/xlib problem key states
I'd like to add a special hotkey feature to the icewm window manager: If the user holds down a (function) key for a configurable amount of seconds a program will be executed. Now my problem is how to query the key states in xlib. My first attempt was using XGrabKey and calculating the time between KeyPress and KeyRelease events but this did not work because of two problems: . Autorepeat must not be set (bad thing) . Other applications do not get the KeyEvents for the grabbed key (even worse) Can anyone tell me how to query the real state of a specific key (Pressed/Released?) with xlib ? Does xkb offer functions for this issue? .. or do I have to hack this directly into the xserver? Thy for any hints!! cheers, pet -- NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien... Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService Jetzt kostenlos anmelden unter http://www.gmx.net +++ GMX - die erste Adresse für Mail, Message, More! +++ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
CONGRATULATION
Our Ref: NKNL/255457003/03. Your Ref:NK-NL/0627/03. Batch No:WD18/0065/03RN. DATE: OCTOBER 17TH, 2003. Dear our treasured winner, RE:LOTTERY BONUS/PROMOTIONS PRIZE AWARDS WINNING NOTIFICATION - FINAL NOTICE . We are pleased to notify you of the release today as dated of the Camlot National Lottery netherland Promotions programs held on the 14th day of October 2003. Your Email attached through a computer ballot system drawn from 25,000 names from Europe, America, Asia, Australia, New Zealand, Middle-East, Africa, and North South America as part of our international promotions program conducted annually to encourage prospective overseas entries. We hope with part of your prize awards, you will take part in our end of year lotto jackpot of $1.3 Billion International Lottery. The result of our computer draw 773 of this day reveals Your Email attached to Ticket Number 025-11476886 with serial number 178 drew the lucky number 18 -19 -21-32-35-39-42 which consequently won the lottery prize awards in the 2nd category. Therefore, you have been approved a lottery jackpot lump sum prize awards winning of $1,140, 850.00 (One Million, One Hundred and Forty Thousand, Eight Hundred and Fifty dollars Only) in cash prize credited to file Ref. No: NKNL/255457003/02. This is from the total prize of $13,286, 320.00 (Thirteen Million, Two Hundred and Eighty Six Thousand, Three Hundred and Twenty dollars) shared among the Thirty Eight overseas lucky winners in this category as part of our promotional program for this year 2003. Your prize awards has been insured in your names and ready for claim. To begin your claims therefore, you are advised on final notice and as a matter of urgency, to contact our licensed and accredited claim agent for your claim with theis information ,below for processing of your prize awards winning and payment to your designated bank account. Contact the, Customer Service Unit, Camelot Agent Inc. Tel:+ 31-627-446999 Email: [EMAIL PROTECTED] Contact person: Mr.John Brown Due to mixed up in some numbers and names and for the purpose of confidentiality, be advised to keep this award notification as secret from public notice until your claim has been processed and your prize money remitted to your designated bank account as this is part of precautionary measures to avoid double claim or misuse of this program by some social miscreants. Hence, your awards winning is confidential as our winners are at liberty to remain completely anonymous until payment is effected to the benefit of the beneficiary. Our staffs are sworn to secrecy, so you will be the only one to know what you've won hence, this notification via this medium (EMAIL) to avoid interception of official letters. On a final note, you are advised to begin your claim immediately hence, all prizes awards must be claimed and disbursed within 21days of this notification as elapse of the scheduled End of Claim date will authorized funds withholding for redirection as abandoned/ unclaimed without notice. Note: To enhance the processing of your claim by our accredited claim agent, you are advised to officially introduce yourself to the claim agent and also provide them with your valid means of your personal identification with a copy of this awards notification for references. CONGRATULATIONS !!! At your disposal, we remain. Mr.Dom Hose Vice president Camelot finance ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Logitech Elite Keyboard Layout
On Mon, 20 Oct 2003, J E Dog wrote: Is this your particular preference? Why yes it is. And it's the most popular preference of most developers working on most software projects who even know how about how to generate patches with diff and apply them with patch also. The majority of developers working on any OSS software that I know, be it XFree86 or something else This is not 'something else'. This is XFree86. There are, at the latest counting, 5 forks of XFree86 code out there. Why don't you spread your good cheer? I've yet to see a single developer of anything stand up and shout that they prefer some other format of diff other than unified diff. I'm not particularly interested in your opinion nor your banter in any case. -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Kernel Module? On second thought...
Mike A. Harris wrote: If DRI is disabled, then the Radeon driver will use the older MMIO mechanism to do 2D acceleration. I don't know what if any of the other drivers will use DRI for 2D or Xvideo currently, however any hardware that supports using DMA/IRQ for 2D accelration or other stuff theoretically at least can use the DRI to do it. I think that's the right model to follow. Cards that can get benefit should use the existing DRM mechanism, even if they don't support 3D. I believe that the i810 uses its DRM for Xv (or maybe it's XvMC...it's something video related). ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [PATCH] Export symbol lists on Linux
On Wed, Oct 15, 2003 at 11:00:23PM +0200, Jakub Jelinek wrote: On Wed, Oct 15, 2003 at 03:06:46PM -0400, David Dawes wrote: For libGL.so, as anonymous version scripts accept wildcards, I think we should use gl* wildcard, as it is too error-prone to list all the gl* functions. Will the wildcard method work for the platforms that currently use the -def.cpp lists? The GL and GLX APIs should be well-defined. No idea about Cygwin and OS2, for now I've just used it in 2 places in GL-def.cpp but it can be expanded. Attached is a first version of the patch against CVS HEAD, which builds, covers all undefined symbols by XFree86 programs/shared libraries which used to be satisfied by the XF86 shlibs and similarly all 5870 programs/shlibs on my disk. The lnxLib.rules changes should work both with old binutils (where version script simply will not be used and all symbols exported) and newer binutils (2001-12-18 and later) where it will be used. I think it is more important first to make sure there are no symbols which ought to be exported but are not than to make sure that no symbols which are not supposed to be exported are visible. That way we can ensure XFree86 will continue working; in later steps symbols can be removed from the export libs as they are analyzed. I've made lots of *-def.cpp changes keyed from __linux__ for now (well, typically OS2 and linux has very similar export sets), because I have no idea what OS2 and Cygwin needs/doesn't need to export and don't want to break them. Also, X11-def.cpp apparently contains two sets of symbols, one for !OS2 !Cygwin !linux (no idea what platform which uses *-def.cpp is it), one for those 3. Either one set should be killed if it is unused, or merged with the other set. The !OS2 !Cygwin symbols appear to have been in the version of these files imported from X11R6.0. I don't know their origin, but they might have been for Win32 builds. The lists need to be divided into the API-defined symbols, platform-independent exceptions that applications and/or other libraries appear to be using, and platform-specific exceptions determined from examination of the relevant library source (some of the symbols in the existing -def.cpp files marked as platform specific are not). We definitely don't want to keep multiple lists. Some symbols that are currently commented out in a platform-specific way, like: -#ifndef __UNIXOS2__ +#if !defined(__UNIXOS2__) !defined(__linux__) XftDrawCorePrepare #endif should be removed because they no longer exist. That's where checks against the API specs (when they exist) and the public library headers and source code are needed. Has anyone done a comparison of these lists against the API specs yet? IMO this is the most significant part of this exercise, combined with the data you have collected from a set of existing applications. David -- David Dawes Founder/committer/developer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [PATCH] Export symbol lists on Linux
I wouldn't be opposed to just wiping out the #ifdef __CYGWIN__ stuff and starting fresh with a test build. I can always put back any platform-specific #if's that turn out to still be valid. Harold David Dawes wrote: On Wed, Oct 15, 2003 at 11:00:23PM +0200, Jakub Jelinek wrote: On Wed, Oct 15, 2003 at 03:06:46PM -0400, David Dawes wrote: For libGL.so, as anonymous version scripts accept wildcards, I think we should use gl* wildcard, as it is too error-prone to list all the gl* functions. Will the wildcard method work for the platforms that currently use the -def.cpp lists? The GL and GLX APIs should be well-defined. No idea about Cygwin and OS2, for now I've just used it in 2 places in GL-def.cpp but it can be expanded. Attached is a first version of the patch against CVS HEAD, which builds, covers all undefined symbols by XFree86 programs/shared libraries which used to be satisfied by the XF86 shlibs and similarly all 5870 programs/shlibs on my disk. The lnxLib.rules changes should work both with old binutils (where version script simply will not be used and all symbols exported) and newer binutils (2001-12-18 and later) where it will be used. I think it is more important first to make sure there are no symbols which ought to be exported but are not than to make sure that no symbols which are not supposed to be exported are visible. That way we can ensure XFree86 will continue working; in later steps symbols can be removed from the export libs as they are analyzed. I've made lots of *-def.cpp changes keyed from __linux__ for now (well, typically OS2 and linux has very similar export sets), because I have no idea what OS2 and Cygwin needs/doesn't need to export and don't want to break them. Also, X11-def.cpp apparently contains two sets of symbols, one for !OS2 !Cygwin !linux (no idea what platform which uses *-def.cpp is it), one for those 3. Either one set should be killed if it is unused, or merged with the other set. The !OS2 !Cygwin symbols appear to have been in the version of these files imported from X11R6.0. I don't know their origin, but they might have been for Win32 builds. The lists need to be divided into the API-defined symbols, platform-independent exceptions that applications and/or other libraries appear to be using, and platform-specific exceptions determined from examination of the relevant library source (some of the symbols in the existing -def.cpp files marked as platform specific are not). We definitely don't want to keep multiple lists. Some symbols that are currently commented out in a platform-specific way, like: -#ifndef __UNIXOS2__ +#if !defined(__UNIXOS2__) !defined(__linux__) XftDrawCorePrepare #endif should be removed because they no longer exist. That's where checks against the API specs (when they exist) and the public library headers and source code are needed. Has anyone done a comparison of these lists against the API specs yet? IMO this is the most significant part of this exercise, combined with the data you have collected from a set of existing applications. David ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Cygwin/XFree86 Bugs?
On Tue, Oct 21, 2003 at 06:34:53PM -0400, Harold L Hunt II wrote: What happens when I assign patches in the Cygwin Xserver project to [EMAIL PROTECTED]? Does an email go out to everyone with CVS commit access? Is there a single person that receives this email? Should I be assigning patches to a specific person to ensure timely commits? Dunno where it goes, just that thankfully I don't receive any of it. The way I understand bugzilla is that people have to go to the web interface looking for stuff. David -- David Dawes Founder/committer/developer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Cygwin/XFree86 Bugs?
On Tue, 21 Oct 2003, David Dawes wrote: On Tue, Oct 21, 2003 at 06:34:53PM -0400, Harold L Hunt II wrote: What happens when I assign patches in the Cygwin Xserver project to [EMAIL PROTECTED]? Does an email go out to everyone with CVS commit access? Is there a single person that receives this email? Should I be assigning patches to a specific person to ensure timely commits? Dunno where it goes, just that thankfully I don't receive any of it. The way I understand bugzilla is that people have to go to the web interface looking for stuff. [EMAIL PROTECTED] is an ML anyone can subscribe to. I am, and, I believe, so is Egbert. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 Core Team member. ATI driver and X server internals. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Cygwin/XFree86 Bugs?
On Tue, Oct 21, 2003 at 10:04:55PM -0600, Marc Aurele La France wrote: On Tue, 21 Oct 2003, David Dawes wrote: On Tue, Oct 21, 2003 at 06:34:53PM -0400, Harold L Hunt II wrote: What happens when I assign patches in the Cygwin Xserver project to [EMAIL PROTECTED]? Does an email go out to everyone with CVS commit access? Is there a single person that receives this email? Should I be assigning patches to a specific person to ensure timely commits? Dunno where it goes, just that thankfully I don't receive any of it. The way I understand bugzilla is that people have to go to the web interface looking for stuff. [EMAIL PROTECTED] is an ML anyone can subscribe to. I am, and, I believe, so is Egbert. Learn something new every day :-). Looks like the subscriber list is publicly viewable (and very small). David -- David Dawes Founder/committer/developer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Cygwin/XFree86 Bugs?
David Dawes wrote: On Tue, Oct 21, 2003 at 10:04:55PM -0600, Marc Aurele La France wrote: On Tue, 21 Oct 2003, David Dawes wrote: On Tue, Oct 21, 2003 at 06:34:53PM -0400, Harold L Hunt II wrote: What happens when I assign patches in the Cygwin Xserver project to [EMAIL PROTECTED]? Does an email go out to everyone with CVS commit access? Is there a single person that receives this email? Should I be assigning patches to a specific person to ensure timely commits? Dunno where it goes, just that thankfully I don't receive any of it. The way I understand bugzilla is that people have to go to the web interface looking for stuff. [EMAIL PROTECTED] is an ML anyone can subscribe to. I am, and, I believe, so is Egbert. Learn something new every day :-). Looks like the subscriber list is publicly viewable (and very small). Where? I see nothing here: http://xfree86.org/lists.html I also get nothing when I try to forge a link to the list: http://www.xfree86.org/mailman/listinfo/developer/ Is there a different mailing list server for bugs.xfree86.org? So, who wants to handle a high volume of patches specific to Cygwin after the 4.4.0 branch? Any volunteers? I would appreciate someone that can commit to a 24 to 48 hour turnaround on committing submitted patches that don't touch other platforms. Thanks, Harold ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Cygwin/XFree86 Bugs?
On Wed, 22 Oct 2003, Harold L Hunt II wrote: Where? I see nothing here: http://xfree86.org/lists.html I also get nothing when I try to forge a link to the list: http://www.xfree86.org/mailman/listinfo/developer/ Is there a different mailing list server for bugs.xfree86.org? Yes, it is a different server. http://bugs.xfree86.org/mailman/listinfo/developer/ Stuart Stuart R. Anderson [EMAIL PROTECTED] Network Software Engineering http://www.netsweng.com/ 1024D/37A79149: 0791 D3B8 9A4C 2CDC A31F BD03 0A62 E534 37A7 9149 ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Sis DRI ?
Is somebody currently working on the SIS DRI driver/port ? I'm new on the list and not as well informed ;) Stjepan Stamenkovic ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Sis DRI ?
Is somebody currently working on the SIS DRI driver/port ? I'm new on the list and not as well informed ;) Stjepan Stamenkovic ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
