OpenGL broken when phone is set to non-English language
Yes you read that well.
Apparently I have an issue with my application framework.
When a device is set to non-English language my OpenGL rendering is broken.
Colors are all wrong and muli-texturing is not working.
Pointer event handling is also somewhat broken which has me thinking there might be something wrong with my window when the phone is not set to English.
Has anyone seen something like that before?
I only provide RSC files no R01 or any other variant.
I can reproduce similar behavior on various Belle phones: E7, E6, 701.
I can't tell if it's a regression introduced in Belle.
Re: OpenGL broken when phone is set to non-English language
I tried the Texture example from the SDK and it does not have that problem.
My framework startup sequence is very similar to those openglex examples.
I just don't get it. Nasty bug this one.
What has the language to do with OpenGL?
I'm guessing my container window get messed up for some reason.
Re: OpenGL broken when phone is set to non-English language
Do you have any text files involved for storing floating point numbers (configuration, perhaps models, colors, normalized coordinates for pointer events)? Mis-parsing numbers can be a reason.
Needless to say, as long as the example works fine the conclusion about OpenGL vs. language setting is not necessarily correct.
It may be useful to check if there are devices not producing this behaviour, after all there have been really some re-structuring in the graphical subsystem around Symbian^3.
Re: OpenGL broken when phone is set to non-English language
Good point Wiz. I do a lot of text parsing in fact the whole scene is defined by text files. I do use TLex extensively. Can I force the local to English in app to fix my parsing?
Re: OpenGL broken when phone is set to non-English language
Just tested that on Vivaz Pro which is S60 5th ed / S^1 and I have the same issue. It must be the parsing.
Re: OpenGL broken when phone is set to non-English language
You made my day Wiz. Just passing the decimal point as parameter to TLex::Val fixed it.
Can I do something to thank you?