You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@royale.apache.org by GitBox <gi...@apache.org> on 2018/03/17 17:52:12 UTC

[GitHub] carlosrovira opened a new issue #133: Beads in a theme's css rule are not processed

carlosrovira opened a new issue #133: Beads in a theme's css rule are not processed
URL: https://github.com/apache/royale-asjs/issues/133
 
 
   My test are with a component that extends a Group and has a css that declared a "iViewBead", the bead is a MXML Bead that creates a simple button
   
   1) Beads in themes are not working, only work if both (component and viewbead) are located in the same lib. Or in other terms, if the component is in a lib and its viewbead is in the theme that doesn't work. I think this is a bug and that case is not considered in the compiler.
   
   If I assign a Bead in a lib, and one in a theme, only the one in the lib is created at runtime. If I remove the one in lib, no bead is created. So the one in the theme is compiled and goes in the theme but is not processed in the final app. 
   
   2) With 1) working, I should be able to have a viewbead in the lib and a viewbead in the theme, and the one in theme be the one used in final app.
   (the one in the lib should not be considered). As well if I have a css rule in the final App that defines another viewbead, that should be processed as well.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services