On Tuesday 23 October 2001 13:34, Lars Gullik Bjønnes wrote: > John Levon <[EMAIL PROTECTED]> writes: > > | On Tue, Oct 23, 2001 at 11:20:06AM +0200, Juergen Vigna wrote: > | > | > Nope the text is copied to the X-clipboard ONLY in a copy/cut operation not > | > on selection. And this is done on purpose because the copiing of selected text > | > to the clipboard can be quite heavy (think of a external-inset which converts > | > a graphics to an ascii drawing!). So this is NO bug it's a feature :) > | > | a gimmicky misfeature (the ascii art thing) shouldn't be blocking a > | useful feature ;) > > but the problem is more general: we don't know what is required by the > external inset to produce ascii.
Is this the code in WorkArea.C: getClipboard(), putClipboard() ? Is it possible to ascertain if the request for getClipboard() comes from outside LyX because a flag is not set? That way we'd automagically have ascii outside of LyX and LyX-text inside. Or am I barking up the wrong tree? Angus
