On Tuesday, July 18, 2017 at 12:06:41 PM UTC-5, vitalije wrote: There are several possibilities for gently introduction of this property. > One would be to replace attribute `_bodyString` with yet another property > which when set directly can issue a warning to user and set the `_sync` > attribute accordingly. That way we can keep backward compatibility and > prepare for transition, and what is more important give users time to find > good use of this new property. >
All true, but now the solution is looking ugly and indirect. > > The other possibility is to make `v.lines` property one way synchronized > i.e. when set it can adjust immediately _bodyString, and when read it can > use g.splitLines(v._bodyString). It can however keep a copy of last > _bodyString that was split, and when asked again if _bodyString is still > the same value, then return last tuple of lines. That can be solution for a > while. It won't break anyone's code, but it can give opportunity to users > to get used on new property. > But doesn't this negate the supposed benefits of the lines property? It might even hurt performance. 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.
