<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
@font-face
{font-family:"Iosevka Fixed SS16";
panose-1:2 0 5 9 3 0 0 0 0 4;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Aptos",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Iosevka Fixed SS16";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Iosevka Fixed SS16"">Yeah, this idea creates more problems that it tries to solve.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Iosevka Fixed SS16""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Iosevka Fixed SS16"">-andy<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Iosevka Fixed SS16""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Iosevka Fixed SS16""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Iosevka Fixed SS16""><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">openjfx-dev <openjfx-dev-retn@openjdk.org> on behalf of Michael Strauß <michaelstrau2@gmail.com><br>
<b>Date: </b>Thursday, October 24, 2024 at 15:57<br>
<b>To: </b><br>
<b>Cc: </b>openjfx-dev@openjdk.org <openjfx-dev@openjdk.org><br>
<b>Subject: </b>Re: [External] : Re: JEP: JavaFX controls in the title bar<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">> Perhaps the header bar should be a part of a new top-level container?<br>
<br>
This would then be the first and only top-level container of JavaFX.<br>
What would happen if you tried to add it to another container?<br>
<br>
It would also make it harder to create certain UIs. Right now it is<br>
pretty easy to place content below, above, or across the HeaderBar<br>
(just layer it in a StackPane), but with HeaderBar being a "top-level"<br>
container, this doesn't work.<br>
<br>
<br>
<br>
> We may or may not need EXTENDED, if for example, the stage can examine whether the scene contains that particular type of container and drops the native title bar, or something like that? (Do we really support setting a different Scene to an existing Stage?)<br>
<br>
Well, applications can change Scenes, so we need to account for that.<br>
While it would be nice if we could detect whether a HeaderBar is used,<br>
and then automatically support that in the native toolkit, we run into<br>
the problem of initialization order:<br>
We need to know at Stage creation time whether the native toolkit<br>
should support custom header bars, but at Stage creation time we might<br>
not now whether the scene graph will contain a HeaderBar at all.<br>
<br>
The only way I can see this work is if we have something like<br>
Stage.initHeaderBar(), with the downside of inventing a second and<br>
independent scene graph that doesn't interact with the main scene<br>
graph. That would be sad, because the single scene graph is one of the<br>
biggest features of JavaFX.<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>