I've got to the point with my MIDlet development where it does everything I want perfectly... under Sun's j2me_wt2.2 emulator. Or at least, to be perfectly honest and exact, it works perfectly with the emulator's QwertyDevice, DefaultGrayPhone and MediaControlSkin. It crashes the DefaultColorPhone horribly, but not until the user is well into using the application - it starts all right under the DefaultColorPhone.
But when I port it onto the device - an HP IPAQ 6515 using IBM's j9 MIDP2.0 implementation, it will not start at all. It appears to fail immediately, with no diagnostics. And, of course, I'm up against deadlines and have to deliver - this application is wanted in the field on Tuesday, which is why I'm working on Sunday. Can anyone give me any advice as to how to get a handle on what's going on? By MIDlet standards this is probably quite a big and sophisticated application - the jar file is 84Kb and contains 24 classes, a few of which are redundant and could be trimmed out - but this shouldn't be a problem on a device which has 57Mb of RAM. -- Simon Brooke :: [EMAIL PROTECTED] :: http://www.weft.co.uk/ Simon Brooke trading as The Web Engineering Factory and Toolworks. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Eclipseme-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/eclipseme-users
