Or, to link up a
file type with an existing PerceivedType, create a new string value named
PerceivedType in the extension key, and set its contents to the name of the
matching perceived type key in the SystemFileAssociations branch.
File Type Doctor (see ???Customize Context Menus for Files,??? earlier in this
chapter) also supports perceived types through its ???scope??? and ???affiliation???
features. For instance, if you try to delete a context menu action
142 | Chapter 3: The Registry
that??™s connected through a perceived type, File Type Doctor displays a confirmation
box that lists the other filename extensions that will be affected by
the change. Likewise, when creating a new action, you can choose the
scope; click the Properties button next to the Scope list to display all the
extensions tied to the current selection.
While you??™re digging around the HKEY_CLASSES_ROOT\SystemFileAssociations
branch in the Registry, you may find some file extension keys here as well,
like HKEY_CLASSES_ROOT\SystemFileAssociations\.png. These look and work
just like the extension keys and file type keys in HKEY_CLASSES_ROOT, discussed
earlier in this chapter, but they??™re used primarily to reference the
Windows Explorer extensions that were preinstalled with Windows. Why
they??™re here instead of in HKEY_CLASSES_ROOT with the rest of the extensions is
not entirely clear, but what is clear is that the SystemFileAssociations
branch is yet another place to look for Registry keys that affect file types.
Pages:
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217