Hi Thanks Alex and Piotr for your valuable information,
very useful. I think we should use part of the things commented here for
Royale Docs Layout page Andrew is preparing.
I think I'm solving the problem, but want to play a bit more and will come
back to this thread to comment my results and
On 12/11/19, 9:56 PM, "Piotr Zarzycki" wrote:
Hi Alex,
Well non of those events were launched
widthChanged/heightChanged/sizeChanged - cause simply I didn't set any
explicit sizes on a component/parent etc, so there wasn't any kind of place
where I could reach out and
Hi Alex,
Well non of those events were launched
widthChanged/heightChanged/sizeChanged - cause simply I didn't set any
explicit sizes on a component/parent etc, so there wasn't any kind of place
where I could reach out and have the solution.
Thanks,
Piotr
czw., 12 gru 2019 o 06:45 Alex Harui
On 12/11/19, 9:26 PM, "Piotr Zarzycki" wrote:
Hi Carlos,
I just wanted to add that even if component is being added to the parent in
HTML doesn't mean that you will have on it their real sizes immediately.
That is true, especially if the parent (or grandparent, etc) is not
Hi Carlos,
I just wanted to add that even if component is being added to the parent in
HTML doesn't mean that you will have on it their real sizes immediately.
Good example is TabBar where I would like to add navigation buttons. [1] In
theory it's simple in order to determine whether we don't
Like Flex, parents size their children.
Unlike Flex, because some changes to HTMLElements and CSS are "immediate" and
not "deferred to a rendering phase", there is no central pump like the Flex
LayoutManager that lays everything out.
Depending on the component set, the components "should"
Hi,
I'm having a hard time with sizes of components.
When I create a component in the "strand" setter the width of that
component reports 0 when debug.
So doing a layout it does with width = 0.
Then component has width = 100% via CSS what means that in real time has
400px
So my question is...
