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 probably shouldn't happen. This model is calling only selectedItemChanged, *selectedIndexChanged. * I'm assuming you are calling "change" event in ArrayListSelectionModel cause you wanted to know whether someone has changed selectedItem and selectedIndex programmatically . If that was the case you should create a bead which listening for events from model and react in specific way. My proposition is: 1) Remove call of change event from Jewel ArrayListSelectionModel 2) Create a bead if you need for operation of programmatic change - in that case do not use in parallel ListSingleSelectionMouseController Thoughts ? Thanks, Piotr wt., 11 gru 2018 o 22:13 Carlos Rovira <[email protected]> napisał(a): > 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 something temporal, or even could be a final change > too depending on the case. > > > El mar., 11 dic. 2018 a las 22:04, Piotr Zarzycki (< > [email protected]>) escribió: > > > I have tried to do point #2 from your options, but when I declare my own > > class: > > > > .nav { > > background-color: #ffffff > > } > > > > 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 <[email protected]> > > napisał(a): > > > > > Hi Piotr, > > > > > > El mar., 11 dic. 2018 a las 17:37, Piotr Zarzycki (< > > > [email protected]>) 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]. Because > Navigation > > is > > > > actually list my background color is white. The question is how to > make > > > my > > > > navigation transparent component transparent? I know that I could > make > > > some > > > > css trick, but maybe you have a better solution. > > > > > > > > > > > each component use to have a css in Jewel and other one in JewelTheme > > (95% > > > of cases) > > > I still need to write some wiki for all of this > > > In the meanwhile, search for file "_navigation.sass". The one in Jewel > > has > > > definitions for beads and use to have some > > > standard css for things regarding "structure" > > > in the _navigation.sass in JewelTheme instead you'll not find almost > any > > > Royale bead, and css more related to colors, animations, fonts, sizes, > > > ....so more "theme" things that people would want to change. > > > > > > There you'll find > > > > > > // Navigation variables > > > .jewel.navigation > > > background-color: #ffffff > > > > > > So, you can do in many ways: > > > > > > 1) Create your own theme with the same structure as JewelTheme and just > > > change this navigation thing > > > 2) just do in your app in you css, since that will be taken instead the > > > JewelTheme > > > > > > Notice that this will change when we implement full dark mode, that > > > navigation still doesn't support since > > > that component was made after I make dark mode and still don't have > that > > > implemented in SASS so > > > compiling SASS will generate a light/dark theme and/or flat/noflat > theme > > > > > > Another question is - Did you notice that Navigation component fire > > change > > > > event two times - whenever you click on the item ? > > > > > > > > > > > Thanks for reporting, I didn't notice, please feel free to fix that, > just > > > take into account that navigation renderer preventdefault to avoid > trying > > > to open a web page. I see this in the way google material solved > > navigation > > > things > > > but maybe could be a better way to do it > > > > > > Thanks! > > > > > > Carlos > > > > > > > > > > > > -- > > > Carlos Rovira > > > http://about.me/carlosrovira > > > > > > > > > -- > > > > Piotr Zarzycki > > > > Patreon: *https://www.patreon.com/piotrzarzycki > > <https://www.patreon.com/piotrzarzycki>* > > > > > -- > Carlos Rovira > http://about.me/carlosrovira > -- Piotr Zarzycki Patreon: *https://www.patreon.com/piotrzarzycki <https://www.patreon.com/piotrzarzycki>*
