On Fri, Jan 15, 2010 at 9:36 AM, zpcspm <[email protected]> wrote: > Consider to patch g.trace() to prefix the error messages it prints with a > timestamp.
I don't thinks this would help much. In your example, and in every other likely example, it's clear enough where message arise. However, your bug report is interesting. Imo, most of the calls to g.app.gui.toUnicode in qtGui.py should be calls to g.u instead. I suspect the message came from a clipboard method such as w.replaceClipboardWith or w.getTextFromClipboard. All other calls get a QString directly from Qt, and converting a QString to a Python unicode string had better not fail or we have real problems. In short, the solution is to eliminate the (incorrect) warning, but call g.u in most places where we do not expect errors. Leo will then throw an exception if an unexpected error does occur. I'll make these changes immediately and we can begin the important (and non-trivial) work of verifying that they are reasonable. Edward
-- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
