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
The application currently uses bundle file extensions to indicate to the system the file types that it handles. This works fine within the application itself but the application should really register it’s interest in the “new” (2011) UTI system. This way stuff like QuickLook plugins could work.
I have a QL plugin that I wrote back in 2009 that no longer works because it uses the old method of registering itself for file types. Once BeebEm has registered the UTIs then the QL Plugin works.
Admittedly, this requires BeebEm to be installed for the plugin to work but that’s a different challenge and not the concern of BeebEm. BeebEm just needs to be a good citizen and declare it’s support for the disk formats in the new way.
It is nothing more than plist changes as far as I am aware as I have already tested it for SSD / DSD. One question is what should the UTIs be?
The application currently uses bundle file extensions to indicate to the system the file types that it handles. This works fine within the application itself but the application should really register it’s interest in the “new” (2011) UTI system. This way stuff like QuickLook plugins could work.
I have a QL plugin that I wrote back in 2009 that no longer works because it uses the old method of registering itself for file types. Once BeebEm has registered the UTIs then the QL Plugin works.
Admittedly, this requires BeebEm to be installed for the plugin to work but that’s a different challenge and not the concern of BeebEm. BeebEm just needs to be a good citizen and declare it’s support for the disk formats in the new way.
It is nothing more than plist changes as far as I am aware as I have already tested it for SSD / DSD. One question is what should the UTIs be?
See: https://stardot.org.uk/forums/viewtopic.php?f=41&t=15718
The text was updated successfully, but these errors were encountered: