You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disabling svifpd.restrictImageTypes allows viewing other image types, which is great. Not sure of the extent of what can work, but just for context it works out of the box in my case for a C++ Image type bound with pybind11 that supports the buffer protocol / can be converted to a numpy array using np.asarray().
However, these "extra types", or at least he one I'm using, do not seem to be supported in the "new" image viewer (which is also great by the way). Would it be easy to add this support?
Not sure if my understaning is correct, but from
(
) it seems like the "other types" work if they are convertible to numpy arrays and are of correct dimensions.
If that is the case, couldn't they use the same visualisation method / data transfer as numpy arrays?
Thanks
The text was updated successfully, but these errors were encountered:
dprov
changed the title
Feature request: Support "non-restricted types" in experimental views
Feature request: Support "non-restricted types" in experimental viewer
Jun 28, 2024
As you can see there, and the function below that is used for pillow images, it is simple enough if it conforms with the asarray protocol.
I would prefer it if it can be checked to be conforming before trying to actually convert it.
Disabling svifpd.restrictImageTypes allows viewing other image types, which is great. Not sure of the extent of what can work, but just for context it works out of the box in my case for a C++ Image type bound with pybind11 that supports the buffer protocol / can be converted to a numpy array using np.asarray().
However, these "extra types", or at least he one I'm using, do not seem to be supported in the "new" image viewer (which is also great by the way). Would it be easy to add this support?
Not sure if my understaning is correct, but from
(
simply-view-image-for-python-debugging/src/python/image_numpy.py
Line 3 in 3695679
If that is the case, couldn't they use the same visualisation method / data transfer as numpy arrays?
Thanks
The text was updated successfully, but these errors were encountered: