nb. The dock title bar icons work fine with Python 3.6.8 and PyQt 5.12.3.
Chris
On Wed, Aug 21, 2019 at 7:49 PM Chris George wrote:
> Curiouser and *curiouser*.
>
> My distribution default is Python 3.6.8 and PyQt 5.12.3. This combination
> works just fine to run Leo and the two outline
Curiouser and *curiouser*.
My distribution default is Python 3.6.8 and PyQt 5.12.3. This combination
works just fine to run Leo and the two outline problems, headline box and
blue background to the left of selected headlines, don't happen.
If I install PyQt5==5.12.2 to my user directory using
Python 3.6.8 and PyQt 5.13.0 display the problems.
Python 3.6.8 and PyQt 5.12.3 do not.
Sigh. Time to read the changelog.
Chris
--
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,
Matt,
What version of PyQt are you using?
With Python 3.6.8 and PyQt version 5.12.3, I do not see the headline lines
or the light blue bits to the left of the selected node.
With Python 3.7.4 and PyQt 5.13.0, I do.
I will fiddle here to see why that might be.
Chris
On Monday, August 19,
Vitalije,
On Wed, Aug 21, 2019 at 5:41 PM vitalije wrote:
> Well I didn't tried too hard to make it more readable. It can be improved.
>
Ok, after looking at it some more, I see that the vnode tree structure
involves only a list of children and a list of parents (one parent for each
clone).
> I'm finding the vnode code harder to read, but if it works better then it
> is better :-). However, is it better because you are the one who wrote it
> instead of me :-), or because it is easier to avoid mistakes using vnodes?
>
Well I didn't tried too hard to make it more readable. It
Thanks vitalije for noticing the position error. I wonder why it only gave
an error on redo and not also for the original operation.
Thanks for the vnode-based code. Based on a quick test, it seems better
than my position based code as I haven't seen any errors on undo/redo.
I'm finding the
For the last several days I have been wondering whether it would possible
to remove many of Leo's so-called official ivars. LeoDocs.leo has details,
in case you are wondering what they are. The idea was that removing them
might simplify Leo's too-complex startup code.
This morning I even
Hello dear All!
Here's my problem.
When I am doing alt+/ (to quickly call dabbrev-expand), select match and
then save the project with ctrl-s - the expanded text disappears.
If I enter some more letters - everything is ok.
I think this is a bug.
--
You received this message because you are
Well after `one_clone = one.clone()`, position `three` becomes invalid,
because `one.clone()` inserts cloned node above the node `three`. If you
add:
three._childIndex += 1
after `one_clone = one.clone()`, there will be no error after executing
script.
If I were you I would make all tree
On Wed, Aug 21, 2019 at 7:39 AM Austin(Xu) Wang wrote:
> ha.. alt-click works.. thanks.
>
You're welcome. Iirc there is an enhancement item to add corresponding
commands to Leo's Window menu, but that hasn't happened yet.
Edward
--
You received this message because you are subscribed to the
Thanks, vitalije. The else part of the 'if 1:' was my failed attempt to
further simplify the failing case.
The error is happening when the code does: insert, clone, move the clone to
the first child of node="two" (which already has one child named "three"),
undo, redo.
I though I might also
ha.. alt-click works.. thanks.
On Wednesday, August 21, 2019 at 5:25:52 PM UTC+7, Edward K. Ream wrote:
>
>
>
> On Tue, Aug 20, 2019 at 10:19 PM Austin(Xu) Wang > wrote:
>
>> Dear All,
>>
>> For some reason, I cannot find my render dock and tabs dock.
>>
> ...
>
>> How to recover those useful
In the first case after `if 1:`
you have called two times child.copy().moveToNext().moveToNext(), while in
the else case you have called it only once.
I have tried with one call in both cases and it works without error.
Vitalije
--
You received this message because you are subscribed to the
In the code I've been writing, there is one particular case which gives an
"invalid position" error when I redo it. I've written some simplified code
which replicates the scenario (even removing the grouped undo allows the
issue to duplicate).
The code performs 3 individually undoable operations:
On Tue, Aug 20, 2019 at 2:18 PM Matt Wilkie wrote:
> I am considering switching to g.app.db for sizing Leo. That is, Leo's
>> main window would open with the size it happened when it last closed,
>> *regardless* of what outlines are being opened. Imo, this would be more
>> intuitive for users.
Sure, I'll do that or figure out the segfault issue sometime this week.
On Tue, Aug 20, 2019 at 7:26 AM Edward K. Ream wrote:
> Unfortunately, I'm not able to run unit tests without getting a segfault.
>>
> Alright. Create a new branch, and I'll run the unit tests there.
>
--
You received
On Tue, Aug 20, 2019 at 10:19 PM Austin(Xu) Wang wrote:
> Dear All,
>
> For some reason, I cannot find my render dock and tabs dock.
>
...
> How to recover those useful windows?
>
Alt-click (right or left click, depending on your platform settings) the
title of any dock. You will see a list
18 matches
Mail list logo
