Closed GoogleCodeExporter closed 9 years ago
This issue was closed by revision r383.
Original comment by cgraef...@gmail.com
on 25 May 2014 at 7:06
This change is generating lots of extra error messages for filters that do not
host their own property pages:
e.g. VMR7 is hosted by Quartz.dll but its property pages are hosted elsewhere -
probably PropPage.dll. IMO it's only worth showing an error if both class
factory and CoCreateInstance creation for the property page fail.
Original comment by mike.cop...@gmail.com
on 28 May 2014 at 9:53
The errors were caused by me having out of date proppage.dll and evrprop.dll
registered.
I'm still unable to display the following EVR property page CLSIDs though:
{109F160B-B6B0-4C9D-9097-856FBEEBDC66}
{EF1C9B46-FAB9-45F7-87CC-CD9B975E294D}
http://msdn.microsoft.com/en-gb/library/windows/desktop/dd407274(v=vs.85).aspx
Original comment by mike.cop...@gmail.com
on 6 Jun 2014 at 1:45
Fixed by r390 : Better error feedback when when getting DLL class factory for
CLSID fails.
Show property page CLSIDs in Properties/Interfaces/ISpecifyPropertyPages
Original comment by mike.cop...@gmail.com
on 6 Jun 2014 at 2:00
Updated by r410 : Prevent spurious error message showing property page of
internal Analyzer filter not attempting class factory creation of any filter
implemented by .EXE module
Original comment by mike.cop...@gmail.com
on 11 Jul 2014 at 3:34
Original issue reported on code.google.com by
cgraef...@gmail.com
on 25 May 2014 at 6:14