On Feb 14, 11:11 am, "Edward K. Ream" <[email protected]> wrote:
> In another thread, I summarized the planned new process as follows: > > QQQ > Rather than the baroque code in g.app.config.getX, each c.config > [object] will contain two "finalized" > settings dicts, one for shortcuts and one for all other settings. To > get a setting, the c.config.getX methods will simply look up the > setting in the appropriate dictionary. > QQQ Rev 4984 contains the new code that computes the global finalized dicts. The code is pretty much as envisioned in the post: look for the g.new_config switch if you are interested in the details. The next steps: 1. Create per-commander finalized settings and shortcuts dicts, probably in g.openWithFileName. 2. Get settings and shortcuts using c.config methods working only on the finalized dicts. All aspects of the new code are, or soon will be, significantly simpler than the old config code. This is an extremely important improvement. > During development, the g.new_config switch will control whether the old or > new config code is in effect. I'll probably set the new_config switch only after the new_load code is nearly complete. It turned out to be easier to do the new_config code before the new_load code. 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.
