The bug in Xorg-server was fixed long ago, but the workaround remains in Xastir. Unfortunately, this is not a work-around that can be tested at configure time and disabled --- the bug is in the X server, not the client, and one cannot know at compile time whether Xastir will be used with an X server that has the bug. Thus we're all stuck with the workaround, even if we're not using an X server that has that bug.
perhaps just add configure _option_ ? if someone is affected, he will just recompile with that option enabled (i.e. --with-broken-xorg ). given dynamics of xastir releases i assume such work-around will suffice for next 10 years ;) -- _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
