On 04/08/2009 05:00 PM, Thomas Dickey wrote:
...
If only the latest release is API-stable, by definition it's not
stable.
On Wed, Apr 08, 2009 at 05:34:48PM -0400, Behdad Esfahbod wrote:
...
This cannot be deduced from that line. You need to review your math.
On Wednesday 08 April 2009
On Thursday 09 April 2009 10:39:47 Alan Cox wrote:
if someone massively resizes a window with backing store (remembering
it can be mostly offscreen) your X server explodes.
Remind us why turning it on for all windows all the time (Composite) is
better than for one window? ;o)
There
On Wednesday 08 April 2009 21:28:47 Alan Cox wrote:
Backing store has long been off by default in Xfree/Xorg. Fundamentally
its a dumb design issue in the concept of backing store - it means the
server has to consume huge amounts of memory keeping copies of stuff and
if someone massively
On Saturday 28 March 2009 17:42:54 Simon Thum wrote:
Rémi Cardona wrote:
...
Can't we work something out with Qt folks?
Good idea, but I think the above sounds like adopting a
what-breaks-gets-fixed policy is the most realistic option. Adam
probably has to say something enlightening.
On Monday 30 March 2009 11:40:33 Simon Thum wrote:
Bill Crawford wrote:
On Saturday 28 March 2009 17:42:54 Simon Thum wrote:
Rémi Cardona wrote:
...
Can't we work something out with Qt folks?
Good idea, but I think the above sounds like adopting a
what-breaks-gets-fixed policy
On Thursday 26 March 2009 06:05:32 Dave Airlie wrote:
Option AccelDFS true
Just out of curiosity, why is this needed? I thought compositing was mostly
just
texturing onto the root window back buffer and could mostly be done in h/w?
--
Bill, also wondering why compositing seems to be slow on
On Wednesday 18 March 2009 15:50:08 Simon Thum wrote:
Dan Nicholson wrote:
Debian (and Ubuntu by proxy) has a patch that makes libtool only add
needed libraries (i.e., those added on the command line) to the
dependency_libs setting in .la files. Unfortunately, I think it still
has a few
On Tuesday 17 March 2009 18:37:37 Marius Gedminas wrote:
...
What about Pyro, then? http://www.pyrodesktop.org/Main_Page
Oh, look, ActiveX!
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
On Wednesday 11 March 2009 08:11:43 Tino Keitel wrote:
As LCDs usually like vertical refresh rates of 60 Hz, you also
shouldn't use a 75 Hz mode.
Most LCDs seem to be capable of 75, and I (alone?) can see the difference, at
least on my Hanns·G monitors at work.
On Thursday 26 February 2009 18:13:01 Dirk wrote:
Well, then you haven't had it re-enabling itself over and over again to
interfere with your games, yet.
Xavier Bestel wrote:
On Thu, 2009-02-26 at 18:58 +0100, Dirk wrote:
People who believe they need an accelerated pointer to click buttons
On Thursday 19 February 2009 12:09:30 Simon Thum wrote:
Sorry for the noise. I haven't found the issue, but a majority of .pc's
in my system doesn't output cflags. So it's something configuration- or
pkc-config related.
In theory a lot of them shouldn't need to, because they're installed in a
On Tuesday 17 February 2009 18:16:49 Jeff Chua wrote:
On Mon, Feb 16, 2009 at 8:46 AM, Thomas Dickey dic...@radix.net wrote:
Patch #242 - 2009/2/15
The window title bar text seems broken in 242. Recompiled 241 and works on
241.
Here's the string that I used to
On Monday 09 February 2009 11:47:44 Jan Engelhardt wrote:
Hi,
I need assistance in finding out just why on earth xorg decides not to
use 1360x768 despite the monitor returning this in the DDC and having
it in the Modes/PreferredMode option.
Xorg.0.log: http://pastebin.ca/1329034
On Wednesday 21 January 2009 11:13:20 Frank de Lange wrote:
Looks to me like X does not use more than 1.7% of CPU so that is not out
of the ordinary. To find out more about where the memory goes you can
install xrestop to see if something leaks somewhere. Either run it
interactivally and
On Sunday 28 December 2008 08:56:50 Matan Drori wrote:
Bump, adding some backtraces:
Dump 1:
#0 _X11TransWritev (ciptr=0x0, buf=0x21b96720, size=1) at
../../lib/xtrans/Xtrans.c:911
#1 0x20093910 in _XSendClientPrefix (dpy=value optimized out,
client=value optimized out,
On Wednesday 10 December 2008 20:12:19 Glynn Clements wrote:
If you want to avoid the situation where large amounts of memory are
allocated for pixmaps, then can't be freed due to other data sharing
the same memory, you're likely to be better off controlling the
allocation of the pixmaps than
On Wednesday 10 December 2008 06:59:13 Matthieu Herrb wrote:
Hi,
in Xserver 1.5.3, when running the ati (radeon) driver in zaphod mode
(ie one X screen per monitor: :0.0, :0.1) the mouse is stuck on the 1st
screen. This is with the mouse driver on OpenBSD (ie no evdev/hal
involved).
It
On Friday 24 October 2008 15:43:44 Bill Crawford wrote:
On Friday 24 October 2008 15:37:57 Mateusz Jan Dominikowski wrote:
BusidPCI:0:1:1
Try 0:1:0
Ignore me, I'm especially blind today.
___
xorg mailing list
xorg@lists.freedesktop.org
18 matches
Mail list logo
