CompositeOperator enum & possible binary incompatibility
Re: CompositeOperator enum & possible binary incompatibility
We tack on any new enums onto the end of the list to avoid problems as you describe. However, there is a better solution. ImageMagick wrappers should use ParseMagickOption() and MagickOptionToMnemonic() which are MagickCore option mapping methods which ensures the wrapper is immune from any future enum changes.
Who is online
Users browsing this forum: Amazon [Bot], Google [Bot] and 5 guests