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 2022/02/21 20:16:13 UTC

[GitHub] [royale-asjs] greg-dove commented on issue #1179: ComboBox - Binding Too Late For selectedItem Display

greg-dove commented on issue #1179:
URL: https://github.com/apache/royale-asjs/issues/1179#issuecomment-1047201304


   So at least a simple workaround might be something like:
   ```
   <fx:Declarations>
           <mx:ArrayCollection id="myDP">
               <fx:Object label="{compute('scp')}" data="scp"/>
               <fx:Object label="{compute('ftp')}" data="ftp"/>
           </mx:ArrayCollection>
   </fx:Declarations>
   ```
   
   And :  
   `<mx:ComboBox  width="250" top="30" dataProvider="{myDP}"/>`
   
   I think that would mean that the earlier bindings should run first, before the dataProvider assignment binding, because iirc they are processed (at startup/addedToParent) in the order of their declaration. I realize that this is not a solution to the actual difference in lifecycle, but something like that might be a simple way to work around the issue on occasion. In reality, because there is no event trigger for the label 'bindings', it might be something that is more suited to a labelFunction in this case (it seems that the label display is the same as the 'data' field value), that is, assuming labelFunction emulation currently works correctly on ComboBox.
   
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@royale.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org