Re: [PATCH] Ugh. The three RRNotify events don't have 'window' at the same offset in the wire structures.
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
On Wed, 2008-08-13 at 10:26 -0400, Adam Jackson wrote: > > Also saw this: 'configTimestamp' from the xRROutputChangeNotifyEvent > > wire structure is never used. In randrproto.h the two fields 'timestamp' > > and 'configTimestamp' have the same comments. If 'configTimestamp' is > > just padding, it should be labeled as such. > > Not sure what this is about. Keith? configTimestamp is leftover from RandR 1.1 semantics where config requests would be ignored if they referred to 'stale' configuration data. That was required because the config data was full of references to indices in the specific set of data returned in the last query. Now that everything uses fairly stable XIDs, I decided that there really wasn't any reason to check that value anymore, and plenty of reasons *not* to, like failed configuration when hot-plug detection was unreliable. -- keith.packard@xxxxxxxxx
Description: This is a digitally signed message part
_______________________________________________ xorg mailing list xorg@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/xorg
[X Forum] [Devices] [XFree86] [XFree86 Newbie] [Site Home] [IETF Annouce] [Security] [Fontconfig] [Bugtraq] [Photo] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Video for Linux] [Linux RAID] [Linux Resources]