On Mon, 23 Nov 2020 08:37:23 +0100, R.Wieser wrote:
JJ,

But that flag is for documents. Not folders.

Where did you read that ?

Yes, I did read the words "file type" in the explanation to the
FTA_NoRecentDocs flag, but did so in context - both knowing that the
"folder" registry entry works 'rather similar' to any other file type as
well as seeing a number of other flags that could easily be referring to
both*.

Also, is there a reason, let alone a good one, to handle files and folders
different for this flag ?

My statement was based on the illogical fact of what Microsoft does.

First of all, files are not folders, and vice versa. Documents are files,
not folders. But Microsoft lump both of them together as documents. Perhaps
they do that for simplicitic sake. Proper or not.

Regarding the `FTA_NoRecentDocs` flag...

In Windows Shell, there are two types of folders: Folder and Directory. i.e.
`HKCR\Folder` and `HKCR\Directory`. Directory refers to file system
directories, and Folder refers to both file system directories and virtual
directories. Virtual directories e.g. `My Computer`, `Control Panel`, etc.

That flag doesn't affect any of both folder types. That's expected, because
folders/directories are not documents.

*no idea what a flag like FTA_NoEditIcon is supposed to do though. Just
tried, but I can't, thru rightclicking, change a .png filetype icon anyway.

I haven't actually tested it yet, but I believe that flag is for preventing
Shell Icon Handler extensions from overriding the icon specified by
`DefaultIcon` registry, or the Shell's default icon handler.

Luckily its not really a problem. Folders are not shown in the "run" -
"recent" list, and on shutdown I have-been-and-still-do scrub the "My Recent
Documents" folder.

Well, that good then.