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
Adds macOS-specific file association settings that allows the registration of
core types, as well as making package types optional.
---------
Co-authored-by: Russell Keith-Magee <[email protected]>
defines the relative priority of this application when it comes to determining which
196
+
application should open an application. Valid values are ``Owner``, ``Alternate``,
197
+
``Default`` and ``None``.
198
+
199
+
Briefcase will default to a role of ``Alternate`` for any known MIME type, and ``Owner``
200
+
for any custom MIME type.
201
+
202
+
``macOS.LSItemContentTypes``
203
+
----------------------------
204
+
205
+
`LSItemContentTypes <https://developer.apple.com/documentation/bundleresources/information-property-list/cfbundledocumenttypes/lsitemcontenttypes>`_ define the
206
+
UTI content types that the app can handle.
207
+
208
+
Briefcase defaults to the the registered UTI type for known MIME types. It will construct a UTI of the form ``<bundle id>.<app name>.<document type id>`` (e.g., ``org.beeware.helloworld.document``) for unknown MIME types.
209
+
210
+
Although macOS technically allows an application to support multiple UTIs per document types, Briefcase can only assign a single content type. The value of ``macOS.LSItemContentTypes`` must be a string, or a list containing a single value.
0 commit comments