The RecordStore implementation is broken on Series60 phones (at least on my Nokia3650 and the emulator as well). When modifying data (setRecord), memory keeps growing and growing and growing.....
...

Yep,

i had a similar issue when using the RecordStore in my app. When overwriting an existing record, the size of your record-store file keeps growing and growing.

The only way around it (that...

You can download if from the main-site: forum.nokia.com (Tools & SDKs Section).

I'm using the Series60 MIDP 1.2.1 and it works very well for me. Its behavior is very close to my 3650.

szymonpiechowicz,

It totally depends on what you want to make.
If you're planning to write a high-speed game and/or a program making use of some features that Java (J2ME/MIDP/...) may not offer,...

If the application makes full use of some of the new and modified MIDP2.0 capabilities, then the answer is "No". You can not run a MIDP2.0 app on a MIDP1.0 device (emulated or real).

Vice-versa...

hi mayankkedia,

Try not to double-post.... Look at my reply here in your other forum-thread:

http://discussion.forum.nokia.com/forum/showthread.php?s=&threadid=40958

I got this reply from you, mayankkedia:

hi..thankx for the reply...
i will be more specific with my problem this time so that u could get a better idea of what i am trying to do..:-
1)i have a...

Your questions are not very specific (no examples, for example).
But let me try... :)

1) When the Runnable's/Thread's run() method has returned, the thread is no longer running, it is no longer...

I don't use the wtk2.1, but the '2' makes me think it is a MIDP2.0 toolkit/sdk...?

(This behavior happened to me... I was using some MIDP2.0 calls..)

If so, make sure that your code does not...

FatalError:
"my array is about 50x16 elements "

That means you need 50 case statements... So, i guess you are not worried about the size of the code (final JAR size), but more about the...

Try this:


int value 1, value2, return;

switch ( value1 )
{
case 0:
{
int[] x = {1,2,3,4,5};

Thank shmoove!

About the final vars: I also meant final instance of final stack variables:



public class Something
{
final int mVar;
// versus

Update: When running on the emulator, these issues do not occur. Only when running on the real device.
I made some changes that allows a phone-call to come in or some other event to be handled...

I agree with Shmoove. But keep in mind that speed and memory-usage are often a trade off (I call this, in line with the "conservation law of energy", the "[i]conservation law of misery[/]".....

Do you want the curve that you get when throwing a ball into the air?:

OK... let's dreg up some math-stuff from highschool :-)


Then, the equation for that could be written as:



x =...

Hello everyone,

I'm writing a MIDlet that is a J2ME emulator of the old Casio FX7000 calculators.
The J2ME emulator executes a Casio program in a separate thread. This allows the user to cancel...

Use this method:

RecordEnumeration RecordStore.enumerateRecords(...)

and on the returned value, use 'nextRecordId()'.

-- Anton.

I can not give you a definite answer. But as far as I know, it is not possible to assign a hot key (or even a short-cut) to a J2ME application. The best you can do is to assign a short-cut to the...

You'll have to flatten out your two-dimensional array into one 1-dimensional array first. I don't know wether your 2-dim array is a square (i.e. each 'row' has the same number of 'columns'), so you...

I'm developing an app using JBuilder 9.
The code has some debug-statements, which are only executed if a constant is set to true:

class Consts{
...
public static final boolean DEBUG =...

Yes I did.

In a first implementation I kept it open until until the program exited. But then I changed it to close the RecordStore immediately after a save/load/etc. It did not make a difference. ...

If you use a List as your screen, call addCommand(...) on that List. This command shows something like 'OK', 'Confirm' or something similar. Handle this command using your commandlistener. When doing...

There are various ways.....
Assign it to a...:

- null 'pointer':
byte[] b = null;

- empty array:
byte[] b= new byte[0];

- array of n uninitialized bytes:

I'm writing a J2ME app to which I just added RecordStore functionality.

Before this, the memory usage of my app was normal. The J2ME heap showed that about 220Kbyte was in use. TaskManager...