One more idea. Possible places of getting out of sync are when user uses some code outside Leo. If that external code is not aware of lines property it will never mess with it and it will never be broken by the presence of this property. The only way this external code can be hurt by this property is when user who is aware of lines property, set lines value and after that leaves v node on its own. It would be enough just to access v.b property just once after setting lines to make it again safe for all external code. Accessing v.b is almost inevitable, Leo itself will almost certainly access this property very soon. To be sure, user can access v.b property at the end of script or command.
IOW, user who uses lines property can use it freely in own script and using official Leo code. When script is finished and v node is to be left for a while, it will be enough just to access once again v.b. Most of the time user is using this property for some series of interventions on v node and during those interventions it is not necessary to sync property every time. But once when interventions are done, forcing sync by accessing v.b will not hurt performance. It can be used like c.redraw call after making some changes in tree. -- 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.
