Przemek Boryka wrote:Hi !
I tested it on real device not emulator, try to deploy application on mobile device, I don't know, maybe emulator doesn't have default Ringtones, I am not sure. Try to export your programme to apk and by USB copy it on mobile device and install it.
:/ Good luck
Just now, I have tested the same code on emulator, it doesn't work for me. I think the emulator do not handling sound system. But I am not sure. :/
Przemek Boryka wrote:Hi!
I wrote two lines of code :
After running the programme I have heard sound, so I think you don't have default ringtones at "content://settings/system" or you made something wrong.
Try put those two lines in new empty android project and test it. You should hear sound.
Eric Pascarello wrote:
That code is wrong.
First it is onload and not onLoad.
It is saying execute the function extendSearch and store whatever it returns to onload.
If your code was window.onLoad = extendSearch;, it would not of run.
Bear Bibeault wrote:Right now, it looks like you are getting the language value from the parameters. Rather, once you know it, store and retrieve it from the session
Bear Bibeault wrote:Store the language selection in the user's session.
Kumaravadivel Subramani wrote:You may have two different property files to be served based on the language change. The same behavior is being followed in frameworks like struts. It would not be a recommendation to use same file for different language.
Paul Clapham wrote:
Johannes Thorén wrote:The program works perfect if i use a list with lets say 20 words.
I'm surprised. It looks to me like you're only putting half of the words into the list. But I suppose that testing wouldn't really expose that sort of error, since selecting random items from half of the words is almost indistinguishable from selecting random items from all of the words.
Jeff Verdegan wrote:No, you don't actually need to read the whole thing into memory at once. Depending on your specific requirements, there are different approaches you could take. However, if you want to start with the simple approach of just reading it all in, then you have two options:
1) Increase the JVM's max available heap at startup time with the -Xmx option. For example, java -Xmx 512m -cp whatever Myclass
2) Start with a smaller file--much, much, much smaller--until you've verified that the logic of your program is correct. This is a good idea regardless of what approach you finally decide on, as it will make testing much simpler.