Register / Login | Desktop view |
Bruce Giles wrote:I'm guessing that the shaded layers were the ones added after the file had been deleted, which would mean that the search function only searches the most recent unshaded layer. Is that correct?
If so, is there a way to search all layers?
Also, I was able to successfully recall the file, but the restore function was "grayed out", even though the preference to capture and recall using admin privileges was turned on, and the pre-authorization option was enabled.
So I did the recall, and of course QRecall told the Finder to open the temp folder where the file was recalled to.
Why couldn't QRecall restore directly to this folder?
James Bucanek wrote:Bruce Giles wrote:I'm guessing that the shaded layers were the ones added after the file had been deleted, which would mean that the search function only searches the most recent unshaded layer. Is that correct?
In a nutshell, yes. The new user interface?yes, it's still in development?will have an "X-Ray" mode that will display, and let you search for, every item that's ever been captured, regardless of whether it exists in last visible layer or not.
If so, is there a way to search all layers?
You'll have to wait for the next version.
Also, I was able to successfully recall the file, but the restore function was "grayed out", even though the preference to capture and recall using admin privileges was turned on, and the pre-authorization option was enabled.
The restore action is disabled when any earlier layers are hidden.
When you hide recent layers (using the bottom shader), you're hiding recent activity and displaying the items as they were captured in the past. When you hide earlier layers (using the top shader) you hide the history of the items and show only the changes, or deltas. Restoring items with earlier layers hidden could result in existing items being deleted, which is too scary to allow, so QRecall disables the command. For an individual file it won't make any difference, but for a package or folder the results could be quite unexpected.
So I did the recall, and of course QRecall told the Finder to open the temp folder where the file was recalled to.
That wasn't the "Recall" command, that was the "Instant Recall" command, which you can get by double-clicking an item or through the menu. Instant recall recalls the item to the temporary folder and then opens it in the Finder. It's intended as a quick, and informal, way of accessing captured items.
Why couldn't QRecall restore directly to this folder?
It can. Select the items and choose Archive > Recall. QRecall will prompt you, using a standard save dialog, for the location to recall the items to.
Or, use the much simpler method of dragging one or more items directly from the archive window to a window in the Finder.
Bruce Giles wrote:Any forecast on when we'll see the new UI?
That wasn't the "Recall" command, that was the "Instant Recall" command, which you can get by double-clicking an item or through the menu.
Right. That's the thing I keep doing by accident, when what I really wanted to do was open a folder in the archive. (Yeah, I know, click the triangle.)