Results 1 to 2 of 2

Thread: Using the LocalizationStageProcessor for state changes

  1. #1

    Default Using the LocalizationStageProcessor for state changes

    Hi All,

    While testing out the LocalizationStageProcessor, I was able to get the correct locale values out of the resource bundle and applied to the components on the stage. I ran into an issue when adding items via a state change (i.e. <mx:AddChild relativeTo="xyz"> <mx:Label ... /> </mx:AddChild>) which looks like it doesn’t fire off the Event.ADDED event so the locales are not applied.

    Is it possible/correct to use the LocalizationStageProcessor when using addchild during a state change?

    Thanks in advance,
    Nick C.

  2. #2
    Join Date
    Dec 2008
    Location
    Brussels
    Posts
    407

    Default seems to be working fine

    Hey Nick,

    I just did a little test with a state change (I added this to the sample application in the SVN trunk as well now, as a proof of concept) and all was working as usual.
    So, I suspect something else is wrong in your code, are you sure the id of the label you're adding is known by the resourceManager.
    So in other words, if your label has an id of 'mylabel' is there a resource string present with the name 'mylabel_text'?

    cheers,

    Roland

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •