Closed GoogleCodeExporter closed 8 years ago
This is caused by registering VSFilter with different names for VSFilter.dll
As far as I know this is intentional behavior. If someone registers VSFilter
under different names, it usually means they don't want it to share settings
with a filter named something differently. We distribute it and expect it to be
registered with the name VSFilter.dll so it can be used interchangeably with
other versions of VSFilter and you don't lose your personal settings.
None of the unique xy-VSFilter settings conflict with other versions of
VSFilter, and the ones that overlap are your personal customized settings which
can be shared by multiple VSFilter versions. Adding INI behavior I don't see
happening either. VSFilter's registry settings shouldn't be touched by the
end-user, and because of UAC on OS like Vista and Win7, you usually don't have
free write access create a file in the VSFilter directory to store settings.
We will not consider changing the registry behavior or adding ini settings
behavior _unless_ either MPC-HC project and/or CCCP also change it. If you
really want this changed, you'll need to make a topic on Doom9
http://forum.doom9.org/showthread.php?t=123537 and CCCP
http://www.cccp-project.net/forums/index.php?board=2.0 and convince them to
change it. If a change is made in one or both projects it will likely be
patched into xy-VSFilter as well.
Setting this to WontFix for the time being. It will be reopened if MPC-HC
and/or CCCP make changes in this area.
Original comment by cyber.sp...@gmail.com
on 18 Nov 2011 at 8:55
Original issue reported on code.google.com by
ved_k...@ymail.com
on 18 Nov 2011 at 5:37