On Sun, Mar 26, 2017 at 11:00 AM, Eric S. Johansson <[email protected]> wrote:
Here is how I would speak it: > > def write (self, root, > kind = '@unknown', > no sentinels = False, > perfect import flag = False, > script write = False, > thin file = False, > two string = False, > ): > > After going through the whole toggle name transformation process, I would > end up with your example: > > def write(self, root, > kind='@unknown', # Should not happen. > nosentinels=False, > perfectImportFlag=False, > scriptWrite=False, > thinFile=False, > toString=False, > ): > > Thanks for this example. normally, this transformation is bidirectional in that I can transform > from string name codename and then back again. I should emphasize that the > transformation between string naming codename is a database lookup, not a > calculation. > I'm not sure I understand the details of what you are doing, but any time there is a database involved you should think of using uA's <http://leoeditor.com/customizing.html#adding-extensible-attributes-to-nodes-and-leo-files>, accessed via p.u. 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
