-
-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add MagickConnectedComponentsImage function #284
Comments
I have no idea. If you want this to work, please could you ask upstream at https://github.com/ImageMagick/ImageMagick something like 'how get the connected components output through the magick wand api? Is this possible to call through the C library?'. |
Thanks for your speedy response, I opened an issue upstream. ImageMagick/ImageMagick#1568 |
Possibly including the details of what you're trying to do i.e. the first code box from above, might be clearer....I think they have a younger volunteer triaging their issues who might not know what you mean. |
Apparently, the parameters are returned through an object (CCObjectInfo?). See https://imagemagick.org/api/magick-image.php#MagickConnectedComponentsImage for more information. |
For reference.
This is going to need thinking about, if nothing else. Theoretically, the correct way to do this would be to add types (i.e. classes) for RectangleInfo PointInfo and probably CObjectInfo as well. |
I can work around the issue by executing the command and capturing the output directly. Feel free to put this on the 'long term todo list' :) |
When converting an image using ImageMagick, you can pass the option connected-components to search the image for areas that are linked through pixels with the same intensity values.
When defining the option
connected-components:verbose=true
, theconvert
command will return something like this:I am wondering on how to get this output from Imagick. I have tried something like this:
Am I close? Is this even possible at the moment? Thanks for helping!
The text was updated successfully, but these errors were encountered: