Hi Bob, Concerning your proposal for "Temporary Attributes", would you, instead, support just having an easy method for you to remove all attributes? This approach would enable you to just invoke a hotkey or menu item to remove the attributes if you opened a Leo file and realized that "old" attributes remained from a previous session.
The ability to retain Cleo attribute settings across Leo editing sessions is important. As an "editor for programmers", Leo provides nodes to break our projects into logical units but Cleo does not have the capability to track the progress of our work across editing sessions due to the fact that Cleo does not retain its attributes within @thin sub-nodes. As a result, Cleo is not currently very useful to track percent complete or other state information of a subsystem, module or class for those using @thin derived files. I hope this will be addressed in the near future. Of course, we could provide a "robust" solution that would enable users to specify whether to retain or auto-delete attributes as needed. Regards, TL --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
