<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal">
<p dir="auto">On 11 May 2020, at 21:05, John DeSoi wrote:</p>
</div>
<div style="white-space:normal"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir="auto">4D forms are stored in .4DForm files which are really just JSON files. I added that extension to the JSON bundle and the .4DForm files properly show in the Finder preview. But they also show "\0\0\0\0" for GetFileInfo. I'm not seeing that my 4D bundle does anything different from the JSON bundle.</p>
</blockquote></div>
<div style="white-space:normal">
<p dir="auto">The stuff in the bundles does not affect Finder’s (or the system’s) treatment of files. For that, it must be in TextMate’s <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">Info.plist</code>.</p>
<p dir="auto">But as 4D already have the correct definitions, this should not be necessary.</p>
<p dir="auto">You can try to run <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">mdls «file»</code>, for example for <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">main.mm</code> I see this:</p>
<pre style="background-color:#F7F7F7; border-radius:5px 5px 5px 5px; margin-left:15px; margin-right:15px; max-width:90vw; overflow-x:auto; padding:5px" bgcolor="#F7F7F7"><code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0" bgcolor="#F7F7F7">kMDItemContentType = "public.objective-c-plus-plus-source"
kMDItemContentTypeTree = (
"public.objective-c-plus-plus-source",
"public.source-code",
"public.plain-text",
"public.text",
"public.data",
"public.item",
"public.content"
)
</code></pre>
<p dir="auto">This indicates that <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">.m</code> has been registered as conforming to <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">public.source-code</code> (which is one of the types handled by TextMate’s Quick Look plug-in).</p>
<p dir="auto">As for <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">GetFile</code> / <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">SetFileInfo</code>, those are legacy, so while they do “fix” it, it’s not how it’s supposed to work.</p>
<p dir="auto">All that said, in the last few days, both file type registration and Quick Look plug-in has stopped working on my own system (macOS 10.15).</p>
<p dir="auto">For example for a .tex file I now get <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">dyn.ah62d4rv4ge81k3p2</code> as its <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">kMDItemContentType</code>.</p>
<p dir="auto">I have tried to reset the launch services database, reboot, etc., but to no avail.</p>
<p dir="auto">This system has always been a little flaky, but maybe with macOS 10.15 it is more flaky than usual…</p>
<p dir="auto">Would you happen to see this on macOS 10.15 as well?</p>
</div>
</div>
</body>
</html>