For GIF files, we have two competing file services (Form class>>#fileReaderServicesForFile:suffix: and AnimatedImageMorph class>>#fileReaderServicesForFile:suffix:) each of which offer to open the file in a morph. This leads to confusion when dragging a GIF file into the image or selecting a GIF file in a FileList:
Maybe we should add an override/shadow mechanism to the file services so that the AnimatedImageMorph file service could replace the first one for the GIF extension.
For GIF files, we have two competing file services (Form class>>#fileReaderServicesForFile:suffix: and AnimatedImageMorph class>>#fileReaderServicesForFile:suffix:) each of which offer to open the file in a morph. This leads to confusion when dragging a GIF file into the image or selecting a GIF file in a FileList:
https://lists.squeakfoundation.org/pipermail/squeak-dev/2022-May/220331.html
Maybe we should add an override/shadow mechanism to the file services so that the AnimatedImageMorph file service could replace the first one for the GIF extension.