Re: Eureka! How to simplify Leo's key handling

On Friday, April 13, 2018 at 11:31:53 AM UTC+1, Edward K. Ream wrote: > > On Thu, Apr 12, 2018 at 12:43 PM, jkn > wrote: > > I have a previous interest in this ... can I remind you of: >> >> https://github.com/leo-editor/leo-editor/issues/423 >> >> and some

Re: Eureka! How to simplify Leo's key handling

On Friday, April 13, 2018 at 5:31:53 AM UTC-5, Edward K. Ream wrote: I am going to put my head down and work on this project until all unit > tests pass regardless of the g.new_keys switch. > Perhaps some other devs can answer newbie questions while I obsess about the code. I expect to get

Re: Eureka! How to simplify Leo's key handling

On Thu, Apr 12, 2018 at 12:43 PM, jkn wrote: I have a previous interest in this ... can I remind you of: > > https://github.com/leo-editor/leo-editor/issues/423 > > and some associated discussions, in particular with me being interested in > distinguishing between

Re: Eureka! How to simplify Leo's key handling

On Thursday, April 12, 2018 at 3:47:12 AM UTC-5, Edward K. Ream wrote: When I awoke just now I saw...how to drastically simplify Leo's key > handling code. > Phase 1 of the project is complete, exactly following the process described in Lesson 7 of LeoU: How to make complex changes to a code

Re: Eureka! How to simplify Leo's key handling

On Thursday, April 12, 2018 at 3:47:12 AM UTC-5, Edward K. Ream wrote: 2. Leo's code that translates user key settings will generate a LeoKey. > To avoid confusion, the class is g.NewLeoKey. - The code that translates Qt keys to [New]LeoKeys instantly collapses in > complexity. > > - Ditto