Hi Serkan,
Compare the DOM Element trees in the debugger. Is the Group getting the same
size in both cases? How about the login form’s size? My guess is that some
component somewhere needs to kick off another layout when the group is added to
the DOM. You can dispatch a “layoutNeeded” event and force a re-layout of the
parent of the component that has the wrong size.
If you can build a simple test case, open a GitHub issue and we’ll take a look.
-Alex
From: Serkan Taş <serkan....@likyateknoloji.com>
Reply-To: "users@royale.apache.org" <users@royale.apache.org>
Date: Wednesday, January 9, 2019 at 1:17 PM
To: "users@royale.apache.org" <users@royale.apache.org>
Subject: Re: Work on Emulation
Hi Alex,
It seems like the form elements without an id is rendered correctly from the
locale resource after your fix.
But, now I have another issue. When using state with includein for a component,
the layout is rendered ugly beside the one without state definition.
The one has definition below (it is the part of the code not all source):
<s:Group width="100%" height="100%" >
<main:LoginForm id="loginForm" />
</s:Group>
[cid:part1.71359BC1.059A3FA6@likyateknoloji.com]
And this is the one with state (the default state is defined in application
header as loggedOutState):
<s:Group width="100%" height="100%" includeIn="loggedOutState">
<main:LoginForm id="loginForm" />
</s:Group>
[cid:part2.FEB67879.166CA048@likyateknoloji.com]
Thanks,
Serkan
3.01.2019 11:34 tarihinde Serkan Taş yazdı:
Thanks Alex,
I am going to work on.
Thanks,
