New Dash Home has different recent apps/files than lenses

[Michael Terry]

I'm using Unity 5.2.0~+bzr1883ubuntu0+626.

The new Dash Home (without the big buttons) shows a different set of recently used apps than the application lens and a different set of recently used files than the files lens.

It also uses different wording for apps ("Recent" vs "Recently Used"). Files uses the same "Recent" wording in both places.

I've attached screenshots.

[Mikkel Kamstrup Erlandsen (kamstrup)]

The hunch right now is that certain combinations of clear+append on a DeeTransaction can result in a reversal of order. This hinges on the fact that the primary difference between the home screen and lens views is that the lens view goes through a DeeTransaction.

(for the record - the correct ordering is seen on the home screen. the lens view has the same items, but reversed)

[Mikkel Kamstrup Erlandsen (kamstrup)]

Maybe I spoke too soon... I've been added new tests for this all over Dee and it is passing them all no sweat (check attached branch for reference if you don't believe me!). Maybe the error is in fact elsewhere...

[Mikkel Kamstrup Erlandsen (kamstrup)]

Bottom line: Unity relies on some subtle ordering mechanisms that are really not a part of the Dee API. In a fartherly moment of forgiveness I made sure that DeeTransaction respected these assumptions.

[Jo-Erlend Schinstad (joerlend.schinstad-deactivatedaccount)]

The files lens still displays results in the opposite direction, so that the oldest files are displayed first. To activate a recently used file, you need to scroll to the bottom of the list. The dash displays it correctly, though. This is really annoying. Hope it'll get fixed soon.

[Jo-Erlend Schinstad (joerlend.schinstad-deactivatedaccount)]

Why invalid?

[Omer Akram (om26er)]

@Jo, that was an issue in Dee and is fixed.

[Jo-Erlend Schinstad (joerlend.schinstad-deactivatedaccount)]

It is not fixed in Precise yet. When will the fix be pushed in updated manager?

[Omer Akram (om26er)]

Hope for thursday, could be after that as well.

[Jo-Erlend Schinstad (joerlend.schinstad-deactivatedaccount)]

Oh, I see. I was worried that it was supposed to be fixed in Precise, and I'm still experiencing the issue. Thanks for clearing that up. :)