Hi all,
The full screen play can be implemented on Nokia devices by using FullCanvas class, but how about the other model of phones? Like Motorola, Samsung, Sony Erricson and etc… If you have done so in any model of these phones, please share your knowledge,thanks…
Sony Ericsson: only on MIDP 2.0 devices (Canvas.setFullScreen)
Motorola: device dependent - sometimes you can just draw to the whole screen using a normal Canvas (ie, T720, A835) as long as you don’t add Commands, and sometimes you have to use the GameCanvas from Motorola’s Gaming API (ie, A920).
As you can see, there is not always a generic way to get full canvas access. A good rule of thumb is to first try to just draw on the full screen with a normal Canvas (possibly ignoring values from getHeight()), and if that doesn’t work look into the documentation and search for different Canvas classes (usually found in the gaming packages when available). Sometimes it’s just not possible (ie, Sony Ericsson T610).
shmoove
I see that one of the most active nokia discussion board members has found his way to javagaming! Welcome shmoove! 
too bad we don’t have any nokia people taking part here or on the nokia board ;D
Thanks darcone.
It was just a matter of time…
A Canvas by default will cover the entire screen. Some phones leave some pixels at the bottom for commands to be displayed and some don’t. It’s a porting issue.
For instance on the Moto T720, the Canvas.getHeight() will tell you 13 less than the real screen size even though it will gladly allow you to draw there.
This is just one of the many things you have to deal with on a phone by phone basis. Porting is part of life in the J2ME world. I wish there were a way around it, but in many cases is just the different screen sizes that kill you.
Wood
Hello guys. I’m new here.
I was looking for a way of porting some Nokia games to other devices.
Actually I am a JAVA novice, and I don’t do the coding. I just gather information for a firend who’s a coder, but is kind’a lazy to browse the web for info.
As you probably know the main issue of porting Nokia games on other phones is the com/nokia/mid/ui/FullCanvas class.
Can anyone tell me its analogic classes for Samsung and Siemens phones?
[quote]too bad we don’t have any nokia people taking part here or on the nokia board ;D
[/quote]
Hey, yes you do!
(Obligatory disclaimers: not in an official capacity, my views may not reflect Nokia’s, etc.).
[quote]Hey, yes you do!
[/quote]
:o :o :o
So there is actually people that can type on a keyboard at Nokia 
Seriously, you guys should increase (or from my point of view allocate) resources to answer questions on the nokia boards. It’s like we’re fumbling around in the blind!
oh, and fix those emulators (particularly “Conflicting stack sizes”) - they’re more broken than the phones (thank god it’s that way around :D).
ahh, that felt good. - not angry or anything, but just a bit frustrated sometimes when I spend waay too many hours on something that turns out to be the fault of the phone or emulator 
Ofcourse. We all have the same ties, some just happen to work for a high profile company
Ditto.
I suspect the reason they don’t participate more actively on the boards is that they have paid support plans, and they want us developers to shell out some cash before we get any help (just a guess, though). If this is really the reason then it is doing a disservice to both the developer community and Nokia. I can’t imagine that they’re seeing too much profit from those paid developer support plans, and it couldn’t cost too much to hire one or two persons to serve as a liaison between the tech people and the board members (like they do at the Sony Ericsson boards). The financial implications either way must be peanuts for a big corporation like Nokia. But what they stand to gain from actively supporting developers for free, isn’t peanuts: plenty of quality software for their platforms.
The logic behind not supporting developers for free is something that I could never understand.
shmoove
To be fair, Nokia do provide far more documentation and tools than any other handset manufacturer. I find it rather impressive how much the give away for free. Although I do agree that the forums aren’t nearly as good. If it wasn’t for shmoove and a few other knowledgeable folk then it would be a complete waste of time visiting there. Perhaps ForumNokia should give out free N-Gages to the most helpful members. ;D
alas the plight of the modern day j2me developer caught between a rock(stable revenue) and hard place(nokia and the likes).
i can see it changing 
or maybe that is just the seasons.
/Cj
Believe it or not but I found the nokia forums to be the best J2ME forums to start with.
Hi there, I am running two threads for a MIDlet. one of them refreshes the screen while the other one hits the server and gets some data from there. after sometimes, my emulator gives “Conflicting stack sizes” error.
I thought it will be a standard and well known problem, but all what google returned was your message.
can u suggest me how to get rid of it?
Check the release note of the Nokia SDK (in it’s docs directory). This is a known issue with the Nokia emulators.
The good news is that it never happens on the phone.
In the release notes the workaround the suggest is to use WAP networking for the emulator. I never actually tried that (sounds like too much hassle), but I found that increasing the heap size (the -heapsize parameter when running the emulator) makes the error happen much less often.
shmoove
I am a bit paranoid about this issue. If memories serve me right, I may have actually seen it on a series40.
Do we know the exact cause? Can 2 threads issue to HTTP calls at the same time or is that an absolute nono?
Thanks,
???
[quote]Check the release note of the Nokia SDK (in it’s docs directory). This is a known issue with the Nokia emulators.
The good news is that it never happens on the phone.
In the release notes the workaround the suggest is to use WAP networking for the emulator. I never actually tried that (sounds like too much hassle), but I found that increasing the heap size (the -heapsize parameter when running the emulator) makes the error happen much less often.
shmoove
[/quote]
[quote]I am a bit paranoid about this issue. If memories serve me right, I may have actually seen it on a series40.
Do we know the exact cause? Can 2 threads issue to HTTP calls at the same time or is that an absolute nono?
Thanks,
???
[/quote]
The exact cause is because most of the nokia emulators are functional, yet buggy as hell.
I don’t know about two threads - theoretically it should be possible, practically - I wouldn’t do it.
Try the new Series 40 Developer Platform 2 (6230 emulator). It’s even more buggy (!!), however I haven’t seen the Conflicting stack sizes on it.
The emulators emulate devices that only have a WAP stack, but your internet connection on your computer uses an HTTP stack. I guess there’s a bug in the conversion somewhere. But on the real phone there is no HTTP stack so this specific bug doesn’t have a reason to happen (don’t worry, you’ll have plenty more bugs to worry about ;)).
Using two threads for http seems risky to say the least. It’s just asking for trouble. Better have only one thread and implement a queue to handle multiple requests.
shmoove