Fayt navigation

Hi there,

I am a new Dopus user so please bear with me.

I prefer navigation using keys whenever possible and fayt seems perfect for this purpose. My only problem is after visiting "Recycle Bin" i can no longer use keyboard navigation to get somewhere else. No matter what fayt shortcut i try there is not any reaction. All inputs are silently ignored. Am i missing something obvious?

Thanks

When in Recycle Bin, push Shift + Return to open the Find-As-You-Type (FAYT) bar, after which you can navigate with it normally.

Alternatively, F4 will activate the location field above the file display, which handles navigation the same as FAYT (aliases like /desktop, and path completion both work the same there, but it can't do other things FAYT can do like run commands).

The reason FAYT has to be opened explicitly, rather than automatically when you start typing, is that the Recycle Bin view is delegated to the Windows shell (Explorer, essentially, but embedded inside a folder tab). This is because it is an unusual folder, where most of the value-adds which Opus brings won't apply (you can only really select, delete or undelete files there, and not much else), and where there might be compatibility issues if we handle it ourselves (it is quite a weird folder, compared to a normal directory). So we leave it to the shell, but that means the shell is also handling keypresses when that folder is active. We can intercept hotkeys like Shift + Return, but normal letters and symbols are left for the shell since it needs to handle them itself, as we can't be sure how it may want to use them.

There are a couple of other folders which are similar, but none that you would do much in except navigate through to parent/child folders. The main ones you might encounter are the Network and root-level \server folders when dealing with network drives. (Once in a \server\share level, or deeper, we handle it natively.)

There are also some virtual folders, specifically Desktop and This PC (aka My Computer), where we offer the choice of our own native handling and delegating to the shell, with native being the default. Those are folders where it made sense for us to provide our own custom view of them, but allow dropping back to Explorer's view if desired for some reason.