diff options
| author | Jamey Sharp <jamey@minilop.net> | 2010-05-06 21:39:43 -0700 |
|---|---|---|
| committer | Jamey Sharp <jamey@minilop.net> | 2010-05-12 18:09:55 -0700 |
| commit | 65cedf39054cf3a1e695e84ac228cce9e8d48097 (patch) | |
| tree | 9a0b41cf70562a6e9e06263486f2fcf1552da46a /xfixes | |
| parent | afcbbd6dfea51c5b0adca0d720edc02ba0c2dc16 (diff) | |
Kill DoChangeGC in favor of dixChangeGC.
This doesn't change any behavior, but it isn't clear whether NullClient
is correct in all cases. As ajax says,
> For most of these changes, I think it's correct to use NullClient,
> since they are server-initiated changes and should not fail for (eg)
> xace reasons. ... At any rate, you're certainly not changing any
> semantics by leaving them all as NullClient, so this patch can't be
> more wrong than before.
Signed-off-by: Jamey Sharp <jamey@minilop.net>
Reviewed-by: Keith Packard <keithp@keithp.com>
Diffstat (limited to 'xfixes')
| -rw-r--r-- | xfixes/region.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/xfixes/region.c b/xfixes/region.c index 2649c06ce..5e1636962 100644 --- a/xfixes/region.c +++ b/xfixes/region.c @@ -642,7 +642,7 @@ ProcXFixesSetGCClipRegion (ClientPtr client) vals[0] = stuff->xOrigin; vals[1] = stuff->yOrigin; - DoChangeGC (pGC, GCClipXOrigin|GCClipYOrigin, vals, 0); + dixChangeGC (NullClient, pGC, GCClipXOrigin|GCClipYOrigin, vals, NULL); (*pGC->funcs->ChangeClip)(pGC, pRegion ? CT_REGION : CT_NONE, (pointer)pRegion, 0); return (client->noClientException); |