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

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.

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

*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

New --window-spot command-line option

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

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

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 >>

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

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

Re: Rough schedule for Leo 6.1

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

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

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

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

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

Re: leo 6.1 user expirience issues

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

Re: What's wrong with render plugin?

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

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

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.

Devs, please don't add commit_timestamp.json

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

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

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

Re: leo 6.1 user expirience issues

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

Re: What's wrong with render plugin?

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.