[GitHub] carlosrovira opened a new issue #337: Bug in MXML with Bindable Constants

[GitBox <gi...@apache.org>]

carlosrovira opened a new issue #337: Bug in MXML with Bindable Constants
URL: https://github.com/apache/royale-asjs/issues/337
 
 
   while creating an example for a new component, I found a bug in MXML with constants. In the following example:
   
   ```
   <j:beads>
           <js:ContainerDataBinding/>
       </j:beads>
   
   <j:Wizard id="wizard">
           <j:WizardPage id="firstPage">
               <j:step>
                   <j:WizardStep name="second_page"
                               nextStep="second_page"
                               initialPage="true"/>
               </j:step>
           </j:WizardPage>
   
           <j:WizardPage id="secondPage">
               <j:step>
                   <j:WizardStep name="{MyModel.SECOND}"
                               previousStep="{MyModel.FIRST}"
                               nextStep="{MyModel.THIRD}"/>
               </j:step>
           </j:WizardPage>
   </j:Wizard>
   ```
   
   Each WizardPage has WizardStep that is a simple class that holds the data used by the component to know what's the previous and next page, and more, so here we have only normal getters and setters.
   
   Now the bug: The first step don't use binding while the second binds constants to the member properties of the class.
   
   I'm finding that at run time using constants with binding Royale fails to retrieve the data, but if I set normal values, the component is capable to access the data and works fine.
   

----------------------------------------------------------------
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