<div dir="ltr"><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jan 31, 2023 at 6:15 PM Andy Goryachev <<a href="mailto:angorya@openjdk.org">angorya@openjdk.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">On Tue, 31 Jan 2023 23:04:50 GMT, Scott Palmer <<a href="mailto:swpalmer@openjdk.org" target="_blank">swpalmer@openjdk.org</a>> wrote:<br>
<br>
> Is it necessary for any application to know about "auto"?<br>
<br>
I actually don't know how the "auto" behaves. From the description it seems the colors might actually change gradually throughout the day, thus making an enum useless and necessitating the use of the actual colors.<br>
</blockquote><div><br></div><div>From <a href="https://support.apple.com/en-ca/guide/mac-help/mchl52e1c2d2/mac">https://support.apple.com/en-ca/guide/mac-help/mchl52e1c2d2/mac</a><br></div><div><div><br></div><div>Auto just changes from light to dark based on the "Night Shift" setting, which uses either a fixed schedule, or sunset. It doesn't have any "in between" modes. Though it does animate the transition of the colors over 1/2 second or so.</div></div><div><br></div><div>The point being that as far as making the application aware of the current state, auto isn't needed. As a preference for within the application (force light or dark, or 'auto' = track the OS setting) it might be useful. I would only include it if the Theme proposal is also going to dynamically track the OS preference and switch Themes for you. It looks like you have that covered by having the application bind to the Platform Preferences value, in which case "auto" would be an application setting rather than a JavaFX platform setting.</div><div><br></div><div>Scott</div><div> </div></div></div>