I finally got around to installing Leo on a Windows machine so that I can compare it against some behavior I have experienced in OS X.
The main troublesome but intermittent issue on OS X is that when I have multiple outlines open in Leo, it sometimes acts on the wrong Node tree. For instance, there are times when I am trying to insert a child node on the outline I am working on and it appears to be doing nothing at all, but inspecting another Outline (opened but not the active tab) I find that the "failed" child node inserts are all present there. What is worse, closing the "other" outline does not fix the focus problem and no Node operations succeed until I restart Leo - further many times after closing the "other" Outline, when I save the focused (still open) Outline, the log says, "saved: [closed-file].leo"
The above has been very difficult to reproduce deliberately, but I have found a way to reproduce consistently a behavior that might be related. This is in no way a critique of the Viewrendered plugin, but I have found that when I have two Outlines open with content that I can use the viewrendered plugin on, in OS X it gets "sticky" and the viewrendered menu actions (e.g. "vr" or "vr-toggle") will only work on one of the Outlines regardless of which one currently has focus. And if I close he Outline that has the "sticky" viewrendered actions, they still will not work on the open Outline. On Windows this behavior is not present.
Perhaps this reproducible behavior may provide some clues to the source of the problem, I suspect it has much to do with the different way OS X and Windows consider Apps/Menus/Windows.
Any suggestions on where to begin to look into the code to track down this issue with OSX would be much appreciated. Or perhaps this qualifies as a bug?
I may try a Linux (Ubuntu) install to see if I can reproduce the behavior there - I suspect Leo will behave more like Windows than OS X in that installation.
-TK