summaryrefslogtreecommitdiff
path: root/fb/fbseg.c
diff options
context:
space:
mode:
authorJamey Sharp <jamey@minilop.net>2010-05-06 21:39:43 -0700
committerJamey Sharp <jamey@minilop.net>2010-05-12 18:09:55 -0700
commit65cedf39054cf3a1e695e84ac228cce9e8d48097 (patch)
tree9a0b41cf70562a6e9e06263486f2fcf1552da46a /fb/fbseg.c
parentafcbbd6dfea51c5b0adca0d720edc02ba0c2dc16 (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 'fb/fbseg.c')
-rw-r--r--fb/fbseg.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fb/fbseg.c b/fb/fbseg.c
index 80ce7404e..80dd48092 100644
--- a/fb/fbseg.c
+++ b/fb/fbseg.c
@@ -250,7 +250,7 @@ fbSetFg (DrawablePtr pDrawable,
{
if (fg != pGC->fgPixel)
{
- DoChangeGC (pGC, GCForeground, (XID *) &fg, FALSE);
+ dixChangeGC (NullClient, pGC, GCForeground, &fg, NULL);
ValidateGC (pDrawable, pGC);
}
}