Description David Pickens 2005-02-22 15:05:01 EST

The name filter mechanism used by the "org.eclipse.ui.propertyPages" extension 
when applied to files (IFile instances) needs to be more dynamic. Consider 
CDT: it permits users to be able to define new file extensions for, say, 
assembly files (e.g., "*.x86asm"). Thus, it needs to be able to dynamically 
alter the name filter. (This problem is a pending "bug" in CDT).

Currently the name filter is purely static, as defined in the extension.

Defining a new IActionFilter class doesn't help. Since the item is adaptable 
to IFile, the RegistryPageContributor class unconditionally uses the 
WorkbenchFile class as the IActionFilter instance.

As a recommendation, define an optional attribute, "filterClass", in the 
org.eclipse.ui.propertyPages that defines a class that implements 
IActionFilter, and arrange to call it so that it can override the current 
behavior.