Hi Edward,
thanks for taking care of my problem. Basically it works. I can load my leo
file again. Minor issues are:
… (after reading the settings)
The input file appears to be corrupted
undefined section: <<24) | (((v)&0xFF00)<<8) | (((v)>>
… (some of them)
uncached read node changed << latLL >>
…
And it creates a node (adding one on every re-call of the leo!) at the
bottom of the outline "Recovered Nodes"
with a couple of nodes
"Recovered node":
old<<xx>
new<<xx>>
All those are not that important and I probably get rid if them. The
undefined section, i.e. results from a node
holding C-code with the << and >> operators (I could well delete em, it s
ugly anyhow :-)
>From my PoV it is fine. If I can pass you any further details, I will be
happy to help on debugging if possible.
Karl
Am Sonntag, 8. Februar 2015 13:07:23 UTC+1 schrieb Edward K. Ream:
>
> On Sun, Feb 8, 2015 at 5:35 AM, Edward K. Ream <[email protected]
> <javascript:>> wrote:
>
>> On Sat, Feb 7, 2015 at 6:50 PM, resi147 <[email protected] <javascript:>>
>> wrote:
>>
>> >
>> my leo file does not longer load.
>>
>
> Fixed at rev
>
> 0c799d4. I have taken care to handle encoding issues properly, but
> problems still could remain.
>
> Please report whether the fix works for you. Thanks.
>
> Edward
>
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
