Hi, Rich.
*begin off-topic Thanks for your kind words. You too, George.I'm a retired guy and I see many of my contemporaries spending untold hours struggling over "brain teasers for old codgers" or something similar, in a vain attempt to keep their brains from aging. My hobby is MLO debugging and view development - it's more challenging and also more fun. So thanks to you guys for saving me from the find-a-word puzzles.end off-topic* First, let me say that you have a remarkable workaround, it is seldom that you find someone willing to dive in to the extent that you have. Admirable work, well done. Second, I was hoping for some way to show that there is a supported feature of Windows view construction that's not supported on Android - this would have provided a basis for requesting Android support. But given the extent to which you hacked the Windows system to get it to do what you want, I do not think that argument would stick. Instead, I think that the opening argument should be that allowing constants such as Now and Today (are there other constants?) in the Field section of a rule would provide significant benefit for little development (given that you have already demonstrated that it executes correctly). If that recommendation would be accepted then the next step would be to look for Android support. Third, this is the part where I tell you that there is some clever way to get what you want out of the Android system until and unless the new feature you want arrives. Sorry, no clever solutions suggest themselves. The only thing I can suggest is that you build a Today-early view that shows tasks due after 8am today but before 8am tomorrow, and also a today-late view that shows tasks due between 8am yesterday and 8am today. Then, start each day using the late view, and at midnight switch to the early view. You can set a reminder for midnight to help you make the switch. That's all I've got. In fact, I was hoping that you might be out running around doing phone MLO during mainstream daytime and on Windows by the time you reach your extended daytime after midnight. In this case you could just use a standard day view on Android, and use your timeshifted view on Windows during the small hours. Fourth and last, given your success at hacking .mfv, do you have any suggestions on how to create a location rule, something like (CurrentLocation IsNearLocation @Context, 2000 meters)? On Tuesday, February 16, 2016 at 5:39:54 AM UTC-5, Rich Gallagher wrote: > > For Android v2 MLO, after I select a .mfv file with a single view > containing "NOW" as the value for "FIELD", the dialog says something like, > "You are about to import the following 0 views..." -- then MLO goes on > normally without importing the view. > > If I try to import a .mfv with multiple views, MLO ignores views that > contain a "NOW" value for "FIELD"--and successfully imports the other views. > > The behavior is the same whether I try to import a .mfv originally created > by Windows MLO or originally created by Android v2 MLO. > > In short, Android v2 MLO apparently ignores any view in a .mfv with a > "NOW" value for "FIELD" -- and keeps operating normally. > > Thanks for putting your brain to this, Dwight! > -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" 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/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/008bb86d-7796-475d-ad89-34c64b33108e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
