J2MEWTK 1.0.2 and J2MEWTK 1.0.3

I think he refers to the importing of classes placed in the "apps/libs" and "apps/<MIDLET>/libs" directories.

and I suspect you are going 2 say no ;-)

1 point i would like to raise with regard to j2mewtk 1.0.3 and its inclusion of the contents of the libs dir into the classpath.

If you modify/replace a jar/zip file in the global libs dir, you have to delete all the classes in tmpclasses and tmplibs before any compiled midlet will use the new jar/zip file. Its incredibly tedious, and a cause of many bugs ;-(

Also; i've found that recompiling a midlet that uses the old version of a global lib will infact replace the new lib file with the old 1 unless you delete the contents of tmplib/tmpclasses.

example.

I have a Midlet 'Defender'

I also have a jar file 'Shared.jar' in the 'apps/lib' dir.

If I replace the Shared.jar with a different version and recompile Defender (without deleting apps/tmplibs and apps/Defender/tmpclasses) Two things will happen

1) Defender will compile using the old Shared.jar

2) the 'new' Shared.jar in apps/lib will be replaced with the an Shared.jar - no idea where it is gettin this old Shared.jar from.

ALSO

an unrelated problem, but equally important.

I have managed to write a midlet that works fine on win9x, but crashes the emulator in win2k.

the error follows.

'zayit.exe'

The instruction at 0x77f8aa57" referenced memory at "0x00000034" the memory could not be "read".

The memory address and instruction are the same everytime.

Do you want me 2 post source?

rob,

Abuse at 2007-7-1 15:01:42 >