Age | Commit message (Collapse) | Author |
|
Even though it probably makes more sense to just strlen() the name, for
some reason there's a nameLen field in XRROutputInfo, so might as well
actually fill it in.
Signed-off-by: Daniel Stone <daniel@fooishbar.org>
Reported-by: Leif Middelschulte <leif.middelschulte@gmail.com>
|
|
Performed with: find * -type f | xargs perl -i -p -e 's{[ \t]+$}{}'
git diff -w & git diff -b show no diffs from this change
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
|
|
Signed-off-by: Fernando Carrijo <fcarrijo@yahoo.com.br>
Acked-by: Tiago Vignatti <tiago.vignatti@nokia.com>
Reviewed-by: Alan Coopersmith <alan.coopersmith@oracle.com>
|
|
As mentioned in bugzilla ticket 28150.
Calling '_XRRValidateCache' with 'improper' arguments results in a SEGV.
This patch adds a parameter validation to the mentioned function.
Signed-off-by: Leif Middelschulte <leif.middelschulte@gmail.com>
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Compiler warning flags should be explicitly set in the makefile
rather than being merged with other packages compiler flags.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
|
|
We didn't treat _XReply failure as fatal. Parsing an xError as a gamma
ramp reply doesn't work that often.
Signed-off-by: Adam Jackson <ajax@redhat.com>
Reviewed-by: Jamey Sharp <jamey@minilop.net>
|
|
Signed-off-by: Adam Jackson <ajax@redhat.com>
Reviewed-by: Jamey Sharp <jamey@minilop.net>
|
|
Signed-off-by: Adam Jackson <ajax@redhat.com>
Reviewed-by: Jamey Sharp <jamey@minilop.net>
|
|
Signed-off-by: Adam Jackson <ajax@redhat.com>
Reviewed-by: Jamey Sharp <jamey@minilop.net>
|
|
Using X_RRGetOutputProperty does not yield success here.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
Warning corrections are either unused symbols or using an
integer as a pointer (generated by sparse).
|
|
* XRRExtensionInfo can be static
* XRRExtensionName is not called XrandrExtensionName
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
f176b2bda103f6f38aabab8207f47a02cc797659 fixed XRRWireToEvent, but
XRREventToWire had the same bug.
Signed-off-by: Julien Cristau <jcristau@debian.org>
|
|
Conflicts:
src/Xrandr.c
|
|
|
|
|
|
Leaving this uninitialized isn't very helpful, and can cause segfaults.
|
|
|
|
|
|
|
|
These parameters are not treated as input. Rename them to make the inner
workings slightly more obvious.
X.Org Bug 14511 <http://bugs.freedesktop.org/show_bug.cgi?id=14511>
|
|
It is easier, and potentially more precise, to compute the inverse in the
server where everything can eventually be kept in floating point form.
|
|
XRRGetCrtcTransform now returns a giant struct containing all of the
transform and filter data.
XRRSetCrtcTransform now accepts filter parameters.
|
|
|
|
XExtensionInfo, XRRExtensionName, XRRFindDisplay, _XRRHasRates and
_XRRVersionHandler are internal to libXrandr. Don't export them.
|
|
CrtcChange events were getting the source 'height' value stored in the
'width' target in both conversion directions.
|
|
|
|
|
|
Be consistent in variable usage:
nbytes = network byte length.
rbytes = memory byte length.
nbytesRead = actual network bytes read.
Malloc rbytes data to pass to _XRead*, but use nbytes as the
amount of data to read (yes, this is insane, welcome to Xlib).
Some of this patch is semi-gratuitous, but the goal is to be consistent
everywhere.
|
|
Previously, XRRQueryOutputProperty90 would return an uninitialized pointer if
num_values was 0.
|
|
XRRFindDisplay must make extension requests that use LockDisplay, so don't
call it with the display locked, instead pass the info around to the
internal functions that were calling it themselves, having acquired the info
before the outer LockDisplay is called.
|
|
XRRGetCrtcInfo was not moving the rotations value from the wire reply
structure to the XRRCrtcInfo being returned, leaving the value uninitialized.
|
|
|
|
They build. More testing seems indicated.
|
|
Conflicts:
configure.ac
|
|
Pending values are transferred to current values at mode set, allowing a
queue of values to accrue in preparation for the modeset operation while
still reporting valid 'current' values for applications.
The set of valid values is also available so applications can present
a reasonable list to the user during configuration.
|
|
Options are to be implemented as properties instead.
|
|
|
|
These should be reviewed by someone with proto clue, which I'm generally
lacking.
|
|
Follows protocol change which places physical size
information in the output rather than (inappropriately)
in each mode line.
|
|
Thanks to Magnus Kessler <Magnus.Kessler@gmx.net> for reporting this
bug and a correct fix.
|
|
|