<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Dec 28, 2022, at 9:51 PM, Michael Hall <<a href="mailto:mik3hall@gmail.com" class="">mik3hall@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Mail.app not receiving for some reason. So from gmail in Safari.<div class=""><br class=""></div><div class="">>The Apple system properties are going to remain as they are, unless e.g. there's some good reason to change the key of a property.<br class=""></div><div class=""><br class=""></div><div class="">OK, good to know. I'm pretty sure -Dapple.laf.useScreenMenuBar=true was made the OS/X application default. I thought some of the other old property functionality had been incorporated in some way or other but might be mistaken.</div><div class=""><br class=""></div><div class="">>Afaik setAboutHandler is the only way to set such a callback. <br class=""></div><div class=""><br class=""></div><div class="">There seems to be some other way because I don't find anywhere I use this. I eliminated all Apple system properties but still get an About... It seems you are correct that eliminating the <a href="http://about.name/" class="">about.name</a> appears to have no impact. Eliminating -<a href="http://dapple.awt.application.name/" class="">Dapple.awt.application.name</a>=HalfPipe and the About menu item no longer shows the application name but rather the unpackaged main class name. The About window is still correct. It includes the application icon, the application name (valid) in bold. Also, Version and Copyright it appears to get from the application Info.plist. Rather a nice default. I could post a screen shot somewhere? Possibly something has been cached for the app by Apple from some time ago? Or I still need to figure out where this comes from. </div><div class=""><br class=""></div><div class="">>Ask the JavaFX mailing list for supporting an About handler if they don't already have it; I believe their mailing list is <a href="mailto:openjfx-dev@openjdk.org" target="_blank" class="">openjfx-dev@openjdk.org</a></div><div class=""><br class=""></div><div class="">OK, this part of the support would be split. Thanks.</div><div class=""><br class=""></div></div></div></blockquote><br class=""></div><div>Fwiw, I did a little more looking at this.</div><div><br class=""></div><div>It seems this…</div><div><br class=""></div><div>_AppEventHandler</div><div>openCocoaAboutWindow(); // if the handler is null, fall back to showing the Cocoa default</div><div><br class=""></div><div>Is what gets the default window that I am seeing.</div><div><br class=""></div><div>It would then almost seem like a javaFX application could do something like…</div><div>static {<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>java.awt.Desktop.getDesktop().setAboutHandler(null);<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>}</div><div><br class=""></div><div>Might work but it doesn’t.</div><div><br class=""></div><div>You can’t compile directly against com.apple.eawt anymore…</div><div>JDK-8160437 : com.apple.eawt.Application is not exported</div><div><br class=""></div><div>So I don;t know if that could work-around.</div><div><br class=""></div><div>I might wonder if it would be easier for the jdk side to get the Desktop invocation to work rather than javaFX rework all that Apple and the jdk already has done from scratch?</div><div><br class=""></div><div>But currently there appears to be no way to include this functionality for a javaFX app. </div><div><br class=""></div><div>Although, I haven’t asked on the javaFX list. Maybe they already figured all this out</div><br class=""></body></html>