ß71: use "/" to open recent documents, the most recent one is not listed as the first #1244

Closed
ybian opened this Issue Nov 27, 2012 · 6 comments

Projects

None yet

3 participants

Contributor
ybian commented Nov 27, 2012

I like to use "/" to open my recent documents, for example, I do the following every day:

Choose "Xcode" -> Hit "/" -> Select a project -> Enter to open it.

The problem is, before ß71, the most recent project was always the first one in the list after "/", but now, it is not, actually it is often listed as the last one.

Could this be a regression?

Owner
skurfer commented Nov 27, 2012

Hmmm. They are in a different order, but I'm not sure why. We added iCloud documents to that list, but I don't think we changed anything for recent documents. I'm not convinced that they're in the "wrong" order now, though. I'll have to see what's going on.

@skurfer skurfer was assigned Nov 27, 2012
Owner

I think something about the string rank was change in ß71. Like
children are ranked according to rank, instead of...whatever it was
before. I guess that makes sense for most things, but not for recent
documents. There you want the most recent one on top.

On Tue, Nov 27, 2012 at 3:43 PM, Rob McBroom notifications@github.com wrote:

Hmmm. They are in a different order, but I'm not sure why. We added iCloud
documents to that list, but I don't think we changed anything for recent
documents. I'm not convinced that they're in the "wrong" order now, though.
I'll have to see what's going on.


Reply to this email directly or view it on GitHub.

Owner
skurfer commented Nov 27, 2012

I think something about the string rank was change in ß71.

Yeah, that's what I was thinking – I'm the one that changed it – but I haven't looked at the code yet to see if the recents are even ranked.

Owner
skurfer commented Nov 27, 2012

They're not ranked. I used an NSMutableSet when adding iCloud documents to the list (so an iCloud document that was also opened recently wouldn't appear twice). Sets don't preserve order. :-( Should be easy enough to fix.

Contributor
ybian commented Nov 29, 2012

@skurfer Thanks for fixing it so soon.

Owner
skurfer commented Nov 29, 2012

No problem. I couldn't remember having to "search" recent documents so often in the past, but couldn't put my finger on it until you brought up a specific point where it changed. Then, knowing that it could be fixed, it really started to annoy me. :-)

@skurfer skurfer closed this in 53ffee8 Nov 29, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment