Re: Poll: Should Xorg change from using Ctrl+Alt+Backspace to something harder for users to press by accident?
Jason Spiro wrote: > What do you think? Should Xorg change this key sequence? Please vote > "yes" or "no". You can add comments too. If you reply only to me by > private mail, I will eventually summarize your reply to the list. Since I do testing on new drivers it would be inconvenient for me. I still absolutely think that xorg should change or disable this key binding by default. When I started using Linux I wanted to try out compiz which uses CTRL-ALT-MOUSE1 to spin the cube with the mouse. I tried all kinds of key combinations to figure out how to rotate the cube with the keyboard. At this point I accidently found ALT-CTRL-BACKSPACE and I did loose data. For me personally, that wasn't so bad because I did not loose any important data and to be honest I've come to like this restart feature a lot. Many other users would not appreciate it though (I think). Ubuntu already had a discussion on this actually and I think they agreed that doing a confirmation UI in GTK would have reverse dependencies (bad) and doing a non-GTK UI would be ugly, so I think they settled on trying to make a delay required by default (i.e. so that they user had to hold CRTL-ALT-BACKSPACE for a few seconds before the machine zaps X). I think making the keybinding configurable would make sense but I also think it should be turned off or have a delay by default. Martin ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Problem with Pixmap Depth for Render extension
Problem: Pixmap Depth from XGetGeometry doesn't agree with XRenderCreatePicture. If I create a Pixmap (XCreatePixmap) with a depth of 24 bits, the request to get the Geometry (XGetGeometry) of the created pixmap returns it as 32. Ok, I can accept that. But if I then use the Pixmap in a call to XRenderCreatePicture with a 32-bit ARGB Picture format, the call fails. It seems that XRenderCreatePicture 'knows' that the Pixmap is really 24 bits, as requested in the Pixmap creation, rather than 32 bits, as returned in the XGetGeometry call. I am simply trying to call XRenderCreatePicture with the correct PictureFormat type for a Pixmap whose depth I do not know. Using XGetGeometry to query that depth seemed like the obvious think to do. Any ideas what is going on here? Dave ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Poll: Should Xorg change from using Ctrl+Alt+Backspace to something harder for users to press by accident?
2008/9/23 Jason Spiro <[EMAIL PROTECTED]>: > > Problem: Many[1] users have killed X by accident.[2] > > Solution idea: Make it harder to kill X by accident. E.g. you could > change the key sequence users must press. > * Maybe require Control+Alt+Backspace then Control-Alt-Y.[3] > * Or require Control+K+X pressed simultaneously. > > What do you think? Here is the problem. You are asking users who think (and subscribe to computer-related mailing lists) to make a decision for non-thinking computer users. > Should Xorg change this key sequence? Please vote > "yes" or "no". No. > You can add comments too. If you reply only to me by > private mail, I will eventually summarize your reply to the list. > The key sequence is one that cannot be presses accidentally. There are many easier ways to hurt oneself or lose data than this way. In fact, I do not want to perform a quadruple bucky to reset my X server. The Emacs users who have similar keyboard shortcuts can be assumed competent enough for the sake of discussion to understand the consequences of what they are doing. They are using Emacs, a program that takes a non-minimal competency level to use. -- Dotan Cohen http://what-is-what.com http://gibberish.co.il א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת ä-ö-ü-ß-Ä-Ö-Ü ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Extra pointer motion with current git xf86-input-synaptics
Since updating to the current git version of xorg-server, inputproto and xf86-input-synaptics I observe extra pointer movements for every event generated by the touchpad. Even when not touching the pad and using the buttons instead the pointer moves 1 pixel to the top-left which each event (x and y coordinate decrease by 1 every time). Equally, each event generated from touching the pad seems to have this extra movement towards the top-left of the screen. Is anyone else experiencing this problem? Best Regards, Magnus Kessler signature.asc Description: This is a digitally signed message part. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: pixman with and without SSE2 benchmarks?
> There is a summary of the performance difference compared to the MMX > code: > > http://www.daimi.au.dk/~sandmann/perf-diff (Twice as fast on many benchmarks.) Note that this is on core 2, which has magnificent SSE performance. I haven't tried it, but I'm willing to bet that on Pentium-M and Pentium 4, the results are similar for SSE and MMX. Juliusz ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [PATCH] Make -nocursor a runtime option to and remove the compile time NULL_ROOT_CURSOR
Hi, On Thu, Sep 25, 2008 at 1:20 PM, David Greaves <[EMAIL PROTECTED]> wrote: > Barry Scott wrote: >> Am I right in thinking this only disables the cursor over the root >> window and not over the whole screen? > Yes. > Individual apps have the ability to remove their own cursor - and can't the > cursor can be managed once X has started? > > This patch covers the tiny time period when the cross is the only thing > visible > on the screen. Pure vanity :) Note the X server doesn't show the cross when starting up anymore. See, http://cgit.freedesktop.org/xorg/xserver/commit/?id=e02f864fdf19a5ab1682336be343c57fdb69ef43 --Ray ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: pixman with and without SSE2 benchmarks?
On 27.09.2008 18:38, Juliusz Chroboczek wrote: >> There is a summary of the performance difference compared to the MMX >> code: >> >> http://www.daimi.au.dk/~sandmann/perf-diff > > (Twice as fast on many benchmarks.) > > Note that this is on core 2, which has magnificent SSE performance. > I haven't tried it, but I'm willing to bet that on Pentium-M and > Pentium 4, the results are similar for SSE and MMX. I'd bet against that :-). Core 2 has magnificent SSE performance indeed, but that's true for MMX just as well. Roland ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Extra pointer motion with current git xf86-input-synaptics
On Sat, Sep 27, 2008 at 06:10:32PM +0100, Magnus Kessler wrote: > Since updating to the current git version of xorg-server, inputproto and > xf86-input-synaptics I observe extra pointer movements for every event > generated by the touchpad. > > Even when not touching the pad and using the buttons instead the pointer > moves 1 pixel to the top-left which each event (x and y coordinate decrease > by 1 every time). Equally, each event generated from touching the pad seems > to have this extra movement towards the top-left of the screen. what hardware do you have? Any special options in xorg.conf/the fdi file? Cheers, Peter ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
