KP> PRIMARY semantics don't really permit that, and it's a large performance KP> problem for some selection types (ever done cut&paste in the gimp?); to KP> fully support selection content, you'd have to fetch every possible KP> representation of the data and store it in a separate agent.
Thanks. The performance issue is clear. What's the semantics problem?
Juliusz
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
