[cyleigh]

I just updated my copy of OF, I now have four copies of every perspective. I removed all my saved perspectives, made some new ones - but they don't seem to take effect. Eg/ My 'work' perspective is sorted by due date and filtered by 'available' according to the perspective window, but when I switch to the perspective it sorts by context and filters by remaining.

[aslo sent via feedback]

[HERMAN]

Originally Posted by cyleigh

I just updated my copy of OF, I now have four copies of every perspective. I removed all my saved perspectives, made some new ones - but they don't seem to take effect. Eg/ My 'work' perspective is sorted by due date and filtered by 'available' according to the perspective window, but when I switch to the perspective it sorts by context and filters by remaining.

[aslo sent via feedback]

I have a similar problem. Is probably due to the filter settings: they don't seem to stick. I can put my main filter (first one) as DUE, but as soon as I quit OF it forgets that.

[dhm2006]

Originally Posted by cyleigh

I just updated my copy of OF, I now have four copies of every perspective. I removed all my saved perspectives, made some new ones - but they don't seem to take effect. Eg/ My 'work' perspective is sorted by due date and filtered by 'available' according to the perspective window, but when I switch to the perspective it sorts by context and filters by remaining.

I don't have extra copies of my perspectives, but the ones I have are not grouped, sorted, or filtered (available vs remaining) properly. Build 94539.

[Leonardo]

The perspectives do not save the filters correctly.
Saving a perspective and calling it again later doesn't restore the state of the filters properly. The perspectives function is broken at the moment.

Revision: 94539

[ext555]

I'm seeing the same thing

[Ward]

Although I have only three perspectives, it's hard to use OmniFocus without them filtering and sorting correctly.

Is it safe to revert to the latest-1 release?

[xmas]

Hey All,

I just noticed this and the next build should have it fixed. Sorry for the inconvenience.