[markbrown00]

I'm not sure I like the way that in the new builds when you group by context in context view, each group header shows the full path of that context. It is a bit cluttered and I'm not sure it really adds any information. You can tell how your selected context is nested from the context sidebar on the left.

[Tony]

I prefer it. In fact just yesterday morning I decided to go in and re-name all of my nested contexts so that their full paths would show up in those headers. A few hours later I downloaded the new build. Talk about cluttered headers! I had to go back and change them all again, but I was glad to do so.

[johnrover]

I'm with Tony

[dansays]

Agreed, I like the change.

[markbrown00]

ah well...looks like I am in the minority...perhaps I need to give my contexts shorter names so it looks less cluttered

...or maybe (says Mark looking sheepish), Omni might make this an optional feature in the final...

[LizPf]

I think it's great! Much nicer to see "Errands:Northwest" than just "Northwest"

Now, if we could have something similar in the Projects column, so I could tell the difference between "Kid 2: Singletons" and my general singleton tasks. I don't think the whole nest in the column would work -- maybe a tool tip thingy with the full path?

--Liz

[AmberV]

Not only do I like it, I need it. Now I don't have to sit there reading task lists to figure out if I'm looking at CompanyOne>Server or CompanyTwo>Server.