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 /mi/miexpose.c | |
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 'mi/miexpose.c')
-rw-r--r-- | mi/miexpose.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/mi/miexpose.c b/mi/miexpose.c index 2072e6a0a..b4d489a7d 100644 --- a/mi/miexpose.c +++ b/mi/miexpose.c @@ -691,9 +691,9 @@ miClearDrawable(DrawablePtr pDraw, GCPtr pGC) rect.y = 0; rect.width = pDraw->width; rect.height = pDraw->height; - DoChangeGC(pGC, GCForeground, &bg, 0); + dixChangeGC(NullClient, pGC, GCForeground, &bg, NULL); ValidateGC(pDraw, pGC); (*pGC->ops->PolyFillRect)(pDraw, pGC, 1, &rect); - DoChangeGC(pGC, GCForeground, &fg, 0); + dixChangeGC(NullClient, pGC, GCForeground, &fg, NULL); ValidateGC(pDraw, pGC); } |