On Friday, October 24, 2014 8:06:38 AM UTC-4, Alexis wrote:
. . .This way my next scheduled task is always under my next ASAP task. I can quickly compare what to do next. What´s your solution for dealing with ASAP vs. scheduled tasks?. . .Alex
Alex, this is an ingenious and nest solution. To describe my approach, I need to distinguish three categories: Your ASAP tasks which have no ties to any specific dates, your scheduled tasks which are nailed to a specific date-time, and something in between: ASAP tasks that do not appear on my to-do list until a certain date, and that may have some date by which they must be done, but within those constraints they are ASAP.
For specifically scheduled tasks I most often schedule appointments on my calendar. If there is some reason why this needs to be set up as a task (eg other tasks are dependent on the completion of this task) I will generally use MLO Reminder to alert me of the start time.
Alexis wrote:
. . .I use Due Date/Times instead of Start Date/Times as those are displayed on the iOS Devices. . .
In line with GTD I use start and due dates as the cannot-be-done-before date and the must-be-done-before date. It would really be a serious problem for me if I were to lose the use of one of these date fields. If you cannot view the start date on your device, I understand that you need to nake accomodations. But I would encourage you to try to find a way to regain the use of both fields. I don't know much about ios devices but I thought that current versions of MLO for IOS included the ability to create custom views - can't you just add the start date to the views where you need it?
-Dwight