Closed tajmone closed 3 years ago
Yes, right now we need to define all DLL functions, even those which will not be used by the plug-in.
This will probably change in future versions of the interface, but in any case to keep backward compatibility with PM v6.5 we'd still need to define them (i.e. stick to interface v1).
Missing info on DLL functions.
I need to understand if DLL functions specifically targeting import or export functionality can be left out entirely in those plug-ins that won't use them — i.e. if these functions still require defining
DLLProcedure
s that do nothing, or if they can simply be omitted since PM wouldn't try to call them after having acknowledged the plug-in supported features via the registration functions.For example, an import plug-in shouldn’t expect any calls to
beginWrite()
orwriteNextImage()
, and an export plug-in shouldn’t expect any calls togetTransparentColor()
orisAlphaEnabled()
.For more info, see also: