https://bugs.freedesktop.org/show_bug.cgi?id=63398
--- Comment #11 from Michael Meeks <michael.me...@novell.com> --- As a workaround, can we not retain the original semantics by hard-coding and categorising events that used to be 'oneway' and calling them in-line exactly as we used to. IIRC 'oneway' was never asynchronous in-process anyway - just a straight synchronous C++ call (surely); so ... surely we just need to come up with a pseudo-oneway annotation in raw-code for those few methods in that module ? Of course, perhaps I'm crack-smoking ;-) failing that we can simulate oneways (if this is some remote connection) by queueing until idle/dispatching in a thread - but I suspect that's horrible overkill and that the above will work [ but I'm an optimist ]. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
