Dear XQuartz team,
Can anyone advise me the way of workaround for bug
#508(http://xquartz.macosforge.org/trac/ticket/508)? I've test latest Xquartz
beta 2, but issue still reproduced. Is this bug will be fixed for the 10
october as it implied by 2.7.0 milestone or would be better if I do some
workaround hack for that in my own code?
_______________________________________________
Xquartz-dev mailing list
Xquartz-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
