![[ERR!]](https://www.gravatar.com/avatar/11df3cf88dcb5385909161d632508ca5?d=identicon&s=40)
202 Views
Let’s imagine that we are creating a Metro style text editor. With help of the pickers users are able to open and save files at any location. But what if the user wants to reopen a file he or she edited last week? Do we need to show the picker and ask him to open file again? It will be nice to have a list of the recently used documents and provide a way to reopen them with one click. Fortunately, WinRT architects thought about this scenario and introduced several classes grouped together within Windows.Storage.AccessCache namespace.
3 comments
dpeterson
10/10/2011 10:02:30 AM
That's pretty awesome. I don't think that the 25 token limit per application is going to be a problem, anything beyond 25 files is probably too cumbersome for the user.
LunarFrog
10/10/2011 10:22:00 AM
It depends... If you are displaying all these files to the user - yes, 25 items will be enough. But if you want to track all the used files internally, for future reuse - this is an issue. Just imagine that your app is a picture aggregator, something like Lightroom. User will want to add any picture once and have an easy access later. But we will be able to do it just for 25 images...
dpeterson
10/10/2011 10:26:18 AM
That's a good point, but I imagine that there's a performance reason for the low number. My guess is that Windows sets up a filewatcher instance in the background for each file registered for future watching. It would be nice, however, if the default was 25 with a configurable maximum.
bradygaster
10/10/2011 2:12:33 PM
I think 25 is a pretty good number, honestly. I can't imagine a longer menu would be as valuable and might even be easier to ignore.