On Sun, Mar 9, 2008 at 2:25 PM, Terry Brown [EMAIL PROTECTED] wrote:
I was wondering if
nullGui / LeoBridge might be ways to test for problems without a
windowing system / gui event threads contributing?
Interesting idea. From the start I figured it was likely a gui shutdown
problem, so it's
On Mar 9, 7:37 pm, Edward K. Ream [EMAIL PROTECTED] wrote:
On Mar 9, 12:04 pm, Edward K. Ream [EMAIL PROTECTED] wrote:
I expect to get all unit tests working solidly in a day or so.
Leo's bzr trunk now contains all the changes needed to get unit tests
working on Linux. Here is what I
On Mar 7, 5:52 am, Edward K. Ream [EMAIL PROTECTED] wrote:
On Mar 6, 11:08 pm, Lon [EMAIL PROTECTED] wrote:
When I first downloaded and tried to install leo the
install script would not run. After trying several things I eventually
noticed that the scripts file format was dos. I
On Mar 6, 6:00 am, Edward K. Ream [EMAIL PROTECTED] wrote:
On Mar 5, 9:47 am, Terry Brown [EMAIL PROTECTED] wrote:
On Wed, 5 Mar 2008 00:03:54 -0800 (PST)
Lon [EMAIL PROTECTED] wrote:
The second case is just a slight variation with the node v7 moved
down to be a child of v5. There
Sounds like examples might help - also be sure to list which plug-ins
you have enabled.
Cheers -Terry
I have put together two leo files that exhibit both of the problems I
mentioned in my first post. In the first case I attempted to have the
following vnodes (no text was added to the text
So you didn't attempt to create clones in either file?
I assume that's the case, because the vnode titles are all different.
But what's weird is that both files contain clones, clones with
different titles. And I also get the infinite loop trying to open the
first file. Looking at it in
The discussion on the failed unit tests in another thread prompted me
to check my python version. Version 2.4 and 2.5 are both installed
with 2.5 being the current one in use. Until I checked I had thought
version 2.4 was the default. I switched over to using version 2.4 and
the two small test
I recently installed 4.4.7 final on a Ubuntu 7.10 system. I was
previously running Leo 4.4.1 on an older debian system without any
problems. With the new version of Leo on the new system it appears
that the leo file is getting corrupted somehow after just a few nodes
are added. Older files which