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
Images can contain EXIF information for camera rotation. This information is read by Intervention Image and an alignment (rotation) is performed based on it. Since version 3 this happens automatically when new image instances are decoded. In version 2, the orientation had to be triggered manually using the orientate() method.
While this may seem convenient, it may not always be desirable. Especially for very large image formats, rotation can consume alot of memory and processing time, which is not always utilized. See #1278
A return to manual auto-alignment after EXIF camera rotation should be discussed.
Keep in mind that a return to manual, will be a breaking change.
What do you think?
The text was updated successfully, but these errors were encountered:
I'm not very familiar with the internal codes of Intervention Image, but I think if you use a flag/option variable with a correct default value, you can keep current behavior and avoid breaking change. something like this:
Images can contain EXIF information for camera rotation. This information is read by Intervention Image and an alignment (rotation) is performed based on it. Since version 3 this happens automatically when new image instances are decoded. In version 2, the orientation had to be triggered manually using the orientate() method.
While this may seem convenient, it may not always be desirable. Especially for very large image formats, rotation can consume alot of memory and processing time, which is not always utilized. See #1278
A return to manual auto-alignment after EXIF camera rotation should be discussed.
Keep in mind that a return to manual, will be a breaking change.
What do you think?
The text was updated successfully, but these errors were encountered: