Hi Carlos,
The binding system in Flex and Royale has always relied on caught exceptions,
so when debugging you often have to turn off "Pause on caught exceptions" which
can make things challenging if you are trying to catch some other caught
exception. It would be an interesting question to
Hi Alex
El jue., 13 dic. 2018 a las 2:00, Alex Harui ()
escribió:
>
> 1) What error do you get with null/undefined in renderers?
Really, the error doesn't show clearly on browsers. I could see that in
Google Chrome going to Sources and in the right panel check "Pause on
caught exceptions"
I
I'm first going to answer Greg's question from the other thread since it is
probably wise to rename this thread.
Greg asked: "Am I right in interpreting what you say as being that there should
be more
event types for binding at the component level? (not just 'change', but
selectedIndexChanged,
There shouldn't be a need to dispatch "change" until someone interacts with
the component. Differentiating between the two usually helps make setup
code simpler. You can assign initial values to things without reacting
everywhere to the change.
The issue in general was related to binding, which
Hi Alex,
regarding Binding Events, our experience is that is a bit more hard to work
with them in Royale than in Flex. The main issues we are experiencing are:
1.- In almost all renderers we need to check for null/undefined while in
flex is not needed:
text="{optionPack ? optionPack.description
I may have missed something, and DispatchChangeOnStartup is a proper bead,
especially for a first attempt, but theoretically, it shouldn't be needed.
There are different categories of events in Flex and Royale. I'm not sure
there is a complete list of categories, but ones that pop to mind are:
I made changes to address some issues, but I no doubt used the wrong
pattern, sorry guys.
I have mainly focused on non-UI code in the past, or custom UI components
without beads in some other work I did last year so 'beads' is still
something I am getting used to (although composition in general
Yep - I just did quick look into the bead and it's essentially have those
things which are currently baked into Model. I hopefully remove that one
and replace things using bead in Jewel Example.
Thanks for adding that!
Piotr
śr., 12 gru 2018 o 13:04 Carlos Rovira napisał(a):
> Hi Piotr,
>
>
Hi Piotr,
just migrated the bead I talked (DispatchChangeOnStartup) from our project
to royale so you can have all the pieces and help you to diagnose the
problem
As I said you Greg did the latest changes on this components so I should as
well read the changes since I didn't have to analyze
Hi Carlos,
Comments inline.
śr., 12 gru 2018 o 10:44 Carlos Rovira
napisał(a):
> Hi Piotr,
>
> This month Greg and I made some changes to get selectedIndex and
> selectedItem work in List, ComboBox and DropDownList. Since Navigation is a
> List in essence, is involved in this changes. We
Hi Piotr,
This month Greg and I made some changes to get selectedIndex and
selectedItem work in List, ComboBox and DropDownList. Since Navigation is a
List in essence, is involved in this changes. We should see how to avoid
the duplicated event without lost the current workflow that now is
Carlos,
I just looked into the problem with double call of change event. You are
using as default ListSingleSelectionMouseController - in navigation
component which is calling "change" event once someone is clicking on item.
However you are doing it again from ArrayListSelectionModel which
Hi Piotr,
but .nav will not do anything. As I write before the right things should be
.jewel.navigation
background-color: transparent
This in you App css will win over the one in the theme.
Didn't try, but that should work, at least is what I do when I want some
quick change to try or
I have tried to do point #2 from your options, but when I declare my own
class:
.nav {
background-color: #ff
}
It's being override by those one from framework. Maybe I have to inherited
from framework classes ?
Thanks, Piotr
wt., 11 gru 2018 o 20:44 Carlos Rovira napisał(a):
> Hi Piotr,
Hi Piotr,
El mar., 11 dic. 2018 a las 17:37, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:
> Hi Carlos,
>
> I have started playing using Jewel lately more serious and have two
> questions related to Jewel Navigation component.
>
> I'm displaying horizontal navigation like that [1].
15 matches
Mail list logo
