On Fri, Jan 20, 2012 at 9:51 AM, Edward K. Ream <[email protected]> wrote:
> When I awoke this morning I realized that creating menus dynamically > might be a good way forward. It was indeed. Recalculating the shortcuts when menus are activated is easy and natural. The following are notes to myself about the remaining work. Feel free to ignore... Last night I saw that the fundamental problem is that config.getShortcut has no hope of working as it is now. The reason is now clear: the configuration data structures for shortcuts are inadequate. Indeed, all shortcuts for a particular context (leoSettings.leo, myLeoSettings.leo or x.leo) are "organized" as a simple list of bindings (represented by a g.Bunch). This has no hope of working. Instead, the configuration data structures must be organized by stroke and by context simultaneously. Only this way can new key bindings properly override existing bindings. The title of this thread keeps being significant. The @test node provides a way of experimenting with new code safely, without the need for a new branch. I'll create a prototype of the new shortcuts data structure in the @test node, and then migrate the (tested!) code into Leo's core. I expect to finish the work today. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
