Re: Languages for WOResourceManager
Re: Languages for WOResourceManager
- Subject: Re: Languages for WOResourceManager
- From: Ramsey Gurley <email@hidden>
- Date: Thu, 07 Jul 2011 20:17:45 -0700
I think it should work if you call setLanguage() on the direct action.
Ramsey
On Jul 7, 2011, at 7:26 PM, Pascal Robert wrote:
> I'm adding an action to a WO app that is 100% DirectAction. That app have its own subclass of WORequest, and when someone switch languages, we do:
>
> ((OSRequest) _context.request()).setBrowserLanguages(val);
>
> Works fine for the localized strings (again, the app have its own method for localization, no Wonder in there). But for images, they keep the "old" language until I call another page. For example, if I switch to English, the strings are find, but the images stays on the French version. If I move to another page, now everything is ok.
>
> So I guess its WOResourceManager who didn't pick up the language change. Which method or array WOResourceManager calls to find localized images when using plain old WOImage?
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden