I still see the error from time to time, but I don't know if it needs a bug report since there doesn't appear to be any harm done. I can post a report the next I can duplicate the error reliably if you think I should.
Rob............... On Wednesday, March 2, 2016 at 6:38:00 PM UTC-5, Edward K. Ream wrote: > > On Tue, Nov 24, 2015 at 1:39 PM, 'Terry Brown' via leo-editor < > [email protected] <javascript:>> wrote: > > On Tue, 24 Nov 2015 10:47:08 -0800 (PST) >> Largo84 <[email protected] <javascript:>> wrote: >> >> > As a practical matter, should I be concerned >> >> about losing data or is this simply a change in the way Leo 'behaves'? >> >> No need to be concerned about losing data other than clipboard content, >> and even then, I'm guessing you won't see any change - some systems >> have two "clipboards", one that you explicitly copy to, and another >> which is just the current selection, I think the last selection made in >> multi-app. scenarios. I'd guess that your normal clipboard will be >> unaffected, and the second one, which doesn't exist in all systems, is >> the one that's bleating. >> >> But Leo will need to be fixed to avoid generating the message. I'm >> guessing QClipboard:: >> >> supportsSelection() might need to be checked. >> > > What's the status of this? Is it worth an official bug report? > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
