Thanks for this Dwight. You lost me at (NOT((Contexts contains.... Ok, just kidding. Thanks for this, will try and apply to see how well I get it to work. Did go through Section 5, but either skimmed to much, or didn't realize I'm looking the views info. But, yes, the advanced stuff is missing big-time.
On Tuesday, 3 November 2015 07:01:35 UTC+2, Dwight Arthur wrote: > > Hi, Riaan. There is actually some pretty good documentation on how to > manage views in section 5.3 of the User's Guide. The most important part is > Task Filtering, section 5.3.2. Unfortunately, the documentation on Advanced > Filtering is sparse, and that's where the really magical stuff happens. The > view you are looking for is an example of a view that requires the use of > Advanced Filtering. > > I'm assuming that you are using the Active Actions view. That would be > good because Active Actions doen't have any Advanced Filters, so we can > just write the filter we need. If you want to use some other view that > starts out with an Advanced Filter then we would need to somehow join the > new rules to the old ones, which is a little more complex. > > Before writing the filter we need to think about what is exactly needed. I > believe it goes like this: > If a task has the @Work context and also has the @Calls context, and if > the @Work context is currently closed, then exclude the task from the view, > regardless of whether the @Calls context is open. > > To say the same thing in formal notation, tasks would pass the filter if: > (NOT((Contexts contains @Work) AND (Contexts contains @Calls) AND (Context > @Work is closed))) > this can be simplified using boolean logic (this is just logic so far, > nothing to do with MLO) to > (contexts does not contain @Calls) OR (contexts does not contain @Work) OR > (context contains @Work and it's open) > > ok, here we go. > 1. Open MLO on Windows > 2. Is the left panel (view properties) showing? If not, hit Alt-F1 to > display it. > 3. We want the left panel to say Views at the top followed by a list of > availableviews. If it shows a view name at the top followed by the specs > for that view, then you should click on the view name once to bring up the > view list. > 4. Find the view Active Actions and click on it to highlight it, them > click on the VIEWS title to bring up the view properties > 5. find the Advanced section in the view properties. If it's collapsed, > click the twistie to expand it. > 6. tick the checkbox for Add Advanced > 7. click the Setup button to bring up the Setup Advanced Filtering window > 8. click the big blue plus sign to add a blank rule > 9. click the first dropdown box and select "contexts" > 10. click the second dropdown box and select "does not contain" > 11. click the third dropdown box and select @Calls > 12. click the fourth dropdown box and select OR > 13. click the blue plus at the end of the line to add another rule > 14. click the first dropdown box and select "contexts" > 15. click the second dropdown box and select "does not contain" > 16. click the third dropdown box and select @Work > 17. click the fourth dropdown box and select OR > 18. click the blue plus at the end of the line to add another rule > 19. click the first dropdown box and select "contexts" > 20. click the second dropdown box and select "contains (consider > open/closed)" > 21. click the third dropdown box and select @Work > 22. click the OK button at the bottom of the popup to save these rules. > 23. At the bottom of the left panel hit Save View and type in a view name, > like Limited Calls > > Done. Now you should be able to select a view "limited calls" and see your > tasks, except that work calls will be hidden when work is closed. > > You may also want to create a new workspace, set this as the default view > for the workspace, and lock the workspace to this default view > > -Dwight > > > > > > > -Dwight > MLO Betazoid on Windows, Cloud and Android SGN2 > On 10/30/2015 6:21 PM, Riaan Eloff wrote: > > Thanks Dwight. I would actually love to mess around with custom views. > Where could I learn more about this? Have read the manual, it does not > seem to say much on the subject. And, can they be used for Android once > created? > > On Friday, 30 October 2015 15:02:35 UTC+2, Dwight Arthur wrote: >> >> Hi, Riann. The thing about MLO is that there are usually several ways to >> handle each issue, and none of them are "right" or "wrong" they are just >> for different people. Sometimes it comes down to whether you would rather >> spend more time and deal with more complexity to craft a solution that >> exactly matches up with the way you work, or do something that is a lot >> easier and simpler and comes close to how you work. >> >> Nick's solution is the simple one in this case. You have to change the >> way you work to tag every call as to whether it's personal or work, and >> then it works. >> >> If you wanted to go for the crafted solution in this case, you would >> create a custom view that's just like the view you are using now, but with >> a filter added to say, basically, that if a task has both "calls" and >> "work" contexts, it is to be displayed only during the hours when "work" is >> open. Then you can go back to tagging tasks "work" if they are for work and >> "calls" if they are calls and MLO will know what to do if they are both. >> It's not hard when you know how, but it involves a plunge into the complex, >> fiddly but incredibly powerful advanced filtering setup. Would you like to >> try this? Let me know and I will step you through it. >> -Dwight >> >> On Friday, October 30, 2015 at 5:42:30 AM UTC-4, Riaan Eloff wrote: >>> >>> Thnx >>> On Oct 30, 2015 10:25 AM, "Nick Clark" <[email protected]> wrote: >>> >>>> The task shows because you have included an active context in it. I >>>> think the only way to prevent this is to have two contexts, "Personal >>>> Calls" and "Work Calls" and set the active times appropriately. You may be >>>> able to include these within the context "Calls" to see the whole picture >>>> when both are active, but i'd need to experiment a bit to see the effect. >>>> >>>> -- > 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] <javascript:>. > To post to this group, send email to [email protected] > <javascript:>. > Visit this group at http://groups.google.com/group/mylifeorganized. > To view this discussion on the web visit > <https://groups.google.com/d/msgid/mylifeorganized/afd36b9f-803d-4bb1-a499-7a2a5a681ca3%40googlegroups.com?utm_medium=email&utm_source=footer> > https://groups.google.com/d/msgid/mylifeorganized/afd36b9f-803d-4bb1-a499-7a2a5a681ca3%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > > > -- 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 http://groups.google.com/group/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/f9230d87-435a-45e1-9791-e9a0b3fdd9f2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
