Hi, I experienced a problem when using the rapid task entry with parsing feature (multiple tasks = one task per line). If the text is too long, it will be cutted and put into the task notes to keep it short. This is basicly a good idea. At the end of my task there are the properties like due date and reminder which I want to be parsed form the string (for e. g. "Post feature request regarding parsing feature 1w -l1w remind me 3d in advance" which will set the due date 1 week into the feature, a lead time of 1 week and set a reminder 3 days before due date is reached). If the task string is short, this works great. But if the task description is too long, then it will be cutted after a specific amound of characters and the properties are not evaluated but are written as is to the notes section, too.
@Andrey: Can this be changed to first parse the string for properties, set the properties, and then cut it off? This would be great. Regards ======= Bedrudin ======= -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" 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/mylifeorganized?hl=en.
