Re: is there any way to disable alt-letter hotkey for top-level menus?

[gar]

Does that mean that if one remove accelerators from menu item's string - Qt
wouldn't be interested?
So the approach with overriding menus is quite fine?
And if so - then the only obstacle is the ugly "Plugins" item which
accelerator is hardcoded somewhere?

пн, 23 сент. 2019 г. в 18:49, Edward K. Ream :

> On Mon, Sep 23, 2019 at 1:43 AM gar  wrote:
>
> Excuse me, you all went into deep tech details and I lost the clue.
>> What does that mean from the user side?
>>
>
> It means that Qt prevents users from binding Alt-keys that are bound to
> menus.  I know of no *reasonable *workaround.  Don't bother messing with
> settings. That can't possibly work.
>
> 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 leo-editor+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/leo-editor/CAMF8tS3BFqPPrFeFAN2ONKrXOFpO82A%3Dt%3D8cYXvg0mUKLBCQEA%40mail.gmail.com
> 
> .
>

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAC%2B8SVyvY5fx-_65UdTOx-09kLbpeiUtsMo%3DivMY8PfV4mGGSw%40mail.gmail.com.

Re: Unpredictable bug: "NewHeadline" instead of actual headline

[SegundoBob]

*I think the bug is in Leo-Editor*

test03 produces the same bug symptom as my unit tests of my compare 
Leo-Editor files:

"NewHeadline" is seen by LeoBridge but the disk file is correct and does 
not contain "NewHeadline".

For test03 errors/loops is larger, but the errors are still unpredictable 
with many error free loops.  For example.

31 loops 18 errors 58% errors/loops

51 loops 32 errors 62% errors/loops

Based on the above evidence, I think the bug is in Leo-Editor.

You can find the three Python files composing test03  here test03 ;>>

*Bug Symptoms*

Each of the following should not be:

The root node has two parents.  Both parents are the hidden root node.  
Ordinarily, the root node has exactly one parent.

The root node is the only node and its headline is "NewHeadline".

Note: I believe that Leo-Editor until recently set new node headlines to 
"NewHeadline", but now in most cases Leo-Editor sets new node headlines to 
"newHeadline" (no capital letter).

*Test run breaking on the first error (test03 modified slightly since this 
run, to exit gracefully and to conditionally insert breakpoints)*

>
> 2019-09-23 14:55:24 /pri/git/leo_bug_demos/2019-09-21-Phantom-NewHeadline
$ ./test03.py
Leo 6.1-devel, devel branch, build 53cf6d1bb1
2019-09-23 10:35:13 -0500

Expected:
0 Headline
0.0 Headline
0.0.0 Headline
0.1 Headline
0.2 Headline
0.2.0 Headline
Actual:
NewHeadline
> 
/pri/git/leo_bug_demos/2019-09-21-Phantom-NewHeadline/check_file.py(117)checkOutline()
-> exit(50)
(Pdb) where
  
/pri/git/leo_bug_demos/2019-09-21-Phantom-NewHeadline/check_file.py(121)()
-> main()
  
/pri/git/leo_bug_demos/2019-09-21-Phantom-NewHeadline/check_file.py(56)main()
-> checkOutline(cmdrT, outline)
> 
/pri/git/leo_bug_demos/2019-09-21-Phantom-NewHeadline/check_file.py(117)checkOutline()
-> exit(50)
(Pdb) l
112  print(hdr)
113  print('Actual:')
114  for hdr in walkList:
115  print(hdr)
116  import pdb; pdb.set_trace()
117  ->exit(50)
118  #@-others
119  
120  if __name__ == "__main__":
121  main()
122  #@-leo
(Pdb) walkList
['NewHeadline']
(Pdb) root

(Pdb) root.v

(Pdb) root.v.parents
[>, >]
(Pdb) root.v.children
[]
(Pdb) root.v.parents[0]
>
(Pdb) root.v.parents[0].children
[]
(Pdb) cmdrT
Commander 140033515115464: 
'/pri/git/leo_bug_demos/2019-09-21-Phantom-NewHeadline/test.leo'
(Pdb) 


-- 
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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/b8987592-742d-4a06-ba98-a0339a47c826%40googlegroups.com.

New --window-spot command-line option

[Edward K. Ream]

This is #1263 .  
Contrary to predictions this turned out to be very easy to do.

Example:  leo --window-spot=50x100

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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/68f6cba6-4799-4d34-abe2-edb51943ed45%40googlegroups.com.

Re: is there any way to disable alt-letter hotkey for top-level menus?

[Chris George]

Hah. That explains a lot. :-)



On Monday, September 23, 2019 at 12:58:53 PM UTC-7, Edward K. Ream wrote:
>
>
>
> On Mon, Sep 23, 2019 at 11:38 AM Chris George  > wrote:
>
>> I have been investigating using --trace=keys.
>>
>> Using chords, like Ctrl+Shift and using Meta as well, I tried the 
>> following key binding in Leo.
>>
>> Ctrl+Meta+Shift+a = spell-find
>>
>> Leo responds in the terminal at startup: Warning: bad shortcut specifier: 
>> 'Ctrl+Meta+Shift+a = spell-find' and the chord does not work.
>>
>
> It's the other way around:
>
> spell-find = Ctrl+Meta+Shift+a
>
> 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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/dd3ae0d3-634d-429c-9f57-67d982900fb9%40googlegroups.com.

Re: is there any way to disable alt-letter hotkey for top-level menus?

[Edward K. Ream]

On Mon, Sep 23, 2019 at 11:38 AM Chris George  wrote:

> I have been investigating using --trace=keys.
>
> Using chords, like Ctrl+Shift and using Meta as well, I tried the
> following key binding in Leo.
>
> Ctrl+Meta+Shift+a = spell-find
>
> Leo responds in the terminal at startup: Warning: bad shortcut specifier:
> 'Ctrl+Meta+Shift+a = spell-find' and the chord does not work.
>

It's the other way around:

spell-find = Ctrl+Meta+Shift+a

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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS2OoHyr5W-X%2BQAw-eq5dSppKR2XsD-5oRzUcwneyaasLQ%40mail.gmail.com.

Re: Rough schedule for Leo 6.1

[Edward K. Ream]

On Saturday, September 21, 2019 at 5:40:22 PM UTC-5, Edward K. Ream wrote:

> I guesstimate that 6.1b1 will be ready sometime between October 15 and 
November 1.

Work on #1093  pyzo 
in Leo may take several weeks, even after the obvious gui bugs are fixed.

So I wouldn't say 6.1 is coming "soon".  It will happen when it happens.

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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/2d2cb431-6b17-4932-a931-d4ced3618d8d%40googlegroups.com.

Re: Devs, please don't add commit_timestamp.json

[Edward K. Ream]

On Mon, Sep 23, 2019 at 8:59 AM Brian Theado  wrote:

> Maybe vitalije still has the old git hook:
>

Or maybe it was Matt, and Vitalije "inherited" the file when he did a merge.

EKR

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS06f6aFmJtxLXX2%2B7CT-UsdhLTUzwjb3JaoeM8aNy9sfg%40mail.gmail.com.

Re: is there any way to disable alt-letter hotkey for top-level menus?

[Edward K. Ream]

On Mon, Sep 23, 2019 at 1:43 AM gar  wrote:

Excuse me, you all went into deep tech details and I lost the clue.
> What does that mean from the user side?
>

It means that Qt prevents users from binding Alt-keys that are bound to
menus.  I know of no *reasonable *workaround.  Don't bother messing with
settings. That can't possibly work.

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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS3BFqPPrFeFAN2ONKrXOFpO82A%3Dt%3D8cYXvg0mUKLBCQEA%40mail.gmail.com.

Re: leo 6.1 user expirience issues

[Edward K. Ream]

On Mon, Sep 23, 2019 at 1:31 AM gar  wrote:

> for me this worked only with docks on linux
> very strange, now it works well
> I did git update since then, maybe that helped
>

One of life's mysteries.  No harm done.

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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS0wVJCAt5Q0KQYaMUkom0tc5R962mu7K7gP3Dg_OZL7qw%40mail.gmail.com.

Re: What's wrong with render plugin?

[Edward K. Ream]

On Mon, Sep 23, 2019 at 1:18 AM gar  wrote:

> excuse me. something went wrong in my mind and it seemed to me that this
> fix doesnt work for render plugin, only affects code highlighting.
> now i checked it out once again and convinced that I was mistaken.
> excuse me once again.
>

Thanks for this.  No harm done.

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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS0HUojmDjZCw5v4NyQ%3Df0AKnePNGe8x1%2BQ68MC9Gfy9Bg%40mail.gmail.com.

Re: Devs, please don't add commit_timestamp.json

[Brian Theado]

Maybe vitalije still has the old git hook:

$ git log -- leo/core/commit_timestamp.json
[...]

commit 65ca5ec3d4a3af17c538026d825fcea782eb5b8a
Author: vitalije 
Date:   Mon Sep 23 08:17:05 2019 +0200
Fixed issue #658

Leo build: 20190923061705


On Mon, Sep 23, 2019 at 7:16 AM Edward K. Ream  wrote:

> Somebody added this file recently.  I suspect it was Matt.
>
> This happens if you are using an old git hook.  Please delete them if
> necessary from leo-editor.git.hooks.
>
> 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 leo-editor+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/leo-editor/5632f465-69a6-42c4-9391-2727ca408c97%40googlegroups.com
> 
> .
>

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAO5X8CyX3Pk-CRST9157nucp7FZ9AaxMsLKJz_hf1B%2BmOBPS1Q%40mail.gmail.com.

Devs, please don't add commit_timestamp.json

[Edward K. Ream]

Somebody added this file recently.  I suspect it was Matt.

This happens if you are using an old git hook.  Please delete them if 
necessary from leo-editor.git.hooks.

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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/5632f465-69a6-42c4-9391-2727ca408c97%40googlegroups.com.

Re: is there any way to disable alt-letter hotkey for top-level menus?

[gar]

Excuse me, you all went into deep tech details and I lost the clue.
What does that mean from the user side?
For now, I created a copy of main @menu and removed all accelerators from 
top-level items.
None of them work except 'Plugins' one, both on Windows and on Linux.
I can live with it, but still want my alt-p back actually :-)
So as I see the problem - there is a solution, but seems like a single menu 
item is hardcoded.
Again, I see the same picture on both systems, and it's the same - how does 
that concerns complex Qt events?

воскресенье, 22 сентября 2019 г., 21:45:44 UTC+3 пользователь Edward K. 
Ream написал:
>
> On Sun, Sep 22, 2019 at 8:37 AM jkn > 
> wrote:
>
> >> The problem was in the traces.  I'll see what I can do with the 
> bindings.
> The --trace=keys traces are now much more informative.
> > Cool - thank you!
>
> Alas, there seems to be an intractable Qt problem, explained in #1344 
> .  Alt-keys 
> generate *only* shortcut-override events, and Qt generates *duplicate* 
> events.  Handling them duplicates almost all key presses.
>
> Googling this problem indicates that no easy solution is likely.  The 
> shortcut-override events come from child widgets, and focus issues are 
> involved.
>
> I could try ignoring duplicate events, but adding state/history to already 
> very complex event filters is asking for trouble.  In short, I know of no 
> reasonable way forward.
>
> Edward
>
> P.S.  There is no problem with making bindings to Alt keys.  The dummy 
> bindings in leoSettings.leo are never used. The problem is capturing the 
> incoming key events.
>
> EKR
>
>

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/f7fddb07-c302-4948-b905-97319b05df33%40googlegroups.com.

Re: leo 6.1 user expirience issues

[gar]

for me this worked only with docks on linux
very strange, now it works well
I did git update since then, maybe that helped

воскресенье, 22 сентября 2019 г., 14:49:01 UTC+3 пользователь Edward K. 
Ream написал:
>
> On Friday, September 20, 2019 at 8:52:08 AM UTC-5, gar wrote:
>
> > Leo's main window cannot be resized less then some height - which is an 
> issue on low-resolution screens
>
> On both Linux and Windows I can resize the screen so the main window is 
> only a few pixels in height and width.  Afaik, #1339 
>  is not needed. 
>
> What platform are you talking about?  Do you see a limit on either Linux 
> or Windows?
>
> 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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/08824901-e259-457b-98a3-0b93513ccd3d%40googlegroups.com.

Re: What's wrong with render plugin?

[gar]

excuse me. something went wrong in my mind and it seemed to me that this 
fix doesnt work for render plugin, only affects code highlighting.
now i checked it out once again and convinced that I was mistaken.
excuse me once again.

пятница, 20 сентября 2019 г., 21:04:17 UTC+3 пользователь Edward K. Ream 
написал:
>
>
>
> On Fri, Sep 20, 2019 at 12:11 PM gar > 
> wrote:
>
> This is still not available in leo-6.1-final. When to expect it?
>>
>
> I have no idea what you mean.  We are on 6.1-devel.  If you have specific 
> complaints about #1287 please take the time to explain clearly what they 
> are.
>
> 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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/b53f4378-e33e-4cbf-8157-a4c4db8ab0e7%40googlegroups.com.