On May 15, 3:49 am, Ville M. Vainio [EMAIL PROTECTED] wrote:
On Wed, May 14, 2008 at 1:34 PM, Ville M. Vainio [EMAIL PROTECTED] wrote:
[qleolite] requires pyqt4. You need to edit the source and set sys.path
accordingly (to leoBridge), because leo-as-package hasn't happened
yet.
I plan to do
On Thu, May 15, 2008 at 4:23 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
This is an initialization problem. Plugins must be careful to load first so
they can set the gui. You can't be using the nullGui, because
nullGui.get_focus is:
def get_focus(self,frame):
return self.focusWidget
On Thu, May 15, 2008 at 7:48 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
I see. Apparently I made a recent change to nullGui.getFocus in the
key-handling branch. The code I suggested should work. Feel free to modify
the trunk.
Done. I get another crash, though (every line is twice):
QQQ
On Thu, May 15, 2008 at 12:36 PM, Ville M. Vainio [EMAIL PROTECTED]
wrote:
On Thu, May 15, 2008 at 7:48 PM, Edward K. Ream [EMAIL PROTECTED]
wrote:
I see. Apparently I made a recent change to nullGui.getFocus in the
key-handling branch. The code I suggested should work. Feel free to
Now shoot this down if it's a nonworkable idea:
What if someone (say, me ;-) decided to port leo to pyqt4, but not
really port the source code - rather, implement a new GUI on top of
leoBridge?
This would not need to be a full-blown leo; just something simple that
displayed the outline in a
What if someone (say, me ;-) decided to port leo to pyqt4, but not
really port the source code - rather, implement a new GUI on top of
leoBridge?
Sounds cool to me, go for it! If I can get qt4 working on windows I'll
be glad to test for you.
Bob
On Wed, May 14, 2008 at 5:34 AM, Ville M. Vainio [EMAIL PROTECTED] wrote:
Now shoot this down if it's a nonworkable idea:
What if someone (say, me ;-) decided to port leo to pyqt4, but not
really port the source code - rather, implement a new GUI on top of
leoBridge?
This would not need
