Messages by pandora808

hey tofu, long time :)

I was trying to get to a snippet that you referred to, about finding the selected index of a list.  the snippet pages are all broken, would you mind posting some literal code example to show what you were talking about?

thanks!

Well, I was just rejected from the Nokia Ovi store because of this.  

I need to either disable orientation flipping (somehow?) or have the softkeys stay where they were.

Can I get any support from the Kuix team?  I'm a paid license holder for our commercial product... if that helps at all.

no reply in 4 months... yeah. it seems so.  last kuix library update was early 2009.

I even bought a license to use kuix, but now it's dead.  Too bad.  It's in production right now on thousands of phones, and I'm happy with that, but it's sad.

It's also to be expected, with the introduction of modern platforms like iphone/android/palmpre, j2me ui solutions like this just aren't as necessary.  Most J2ME developers I know have, or are migrating to android/iphone.  I'm still doing J2ME work fulltime, but doing Palm (WebOS) stuff in my spare time. 

J2ME is dying... and it will take with it all the great projects like Kuix and GlassBox.

I know exactly what you're talking about, i dealt with the on the nokia 5800 and nokia n97.

the problem is that there's a hardcoded threshold in Kuix that determines if a touch event is a tap or a drag.  5 pixels.  So if you touch the screen and move <5 pixels and release it's a "tap" event, >= 5 pixels and it's a "drag" event.

this becomes a problem on high resolution displays when you can EASILY move 5px with your finger without even knowing it.

so what I did is change that hard coded value to a variable with an accessor method that I can change in runtime (and configured at buildtime for when i'm building for a highrez touch device)

if you look in KuixCanvas.java in pointerDragged()

change:

if (pointerDragged || Math.abs(x - pointerPressedX) > 5 || Math.abs(y - pointerPressedY) > 5) {

to

if (pointerDragged || Math.abs(x - pointerPressedX) > touchDragThreshold || Math.abs(y - pointerPressedY) > touchDragThreshold) {

then add:

private int touchDragThreshold = 5;
public void setTouchDragThreshold(int i) {
     touchDragThreshold = i;
}

so by default it behaves like out-of-the-box Kuix.  But for my nokia 5800 (360x480) I set that value to 20 and it improved the usability by huge amounts.

hope that helps! if not you're screwed :P

-pandora

The biggest problem I have with this is that the softkeys also move with the screen adjustment.  this obviously puts the onscreen-softkeys on a side of the screen where they no longer match up with the hardkeys of the phone.

any work-around for that?  (i just failed QA on the nokia appstore because of this)

there are two problems with the first solution:

1) the user can press "ok" of the alert and close it, even though the search is still waiting for response

2) it doesn't run the time-intensive search on a secondary thread, locking all operations on the UI and potentially crashing the entire application

it's very important to do things like network calls, RMS activity, etc on a secondary thread, on some phones it will lock the entire application hard if you don't.  i know my solution is a little less readable, but it is more appropriate for your particular case

if you're doing any lengthy operation, you should be doing it on a secondary thread, and not locking the UI/event thread the way you are in your example.

here's one way to do it, which shows an alert that the user cannot close until the threaded operation is finished, when it closes itself:

Popup pop = Kuix.showPopupBox(null, -1, "searching...", null, null, null, null, null);

new Thread(new Runnable() {

    public void run() {

        /** your search that may take a few seconds **/

        pop.remove();

    }

}).start();

i've experienced this as well.  I had to disabled transitions in my application because of this.  It seems like the text animation shouldn't start until the transition state is complete.

I also had to modify KuixCanvas to accept the keys to come through the canvas, so i had to run a custom kuix jar. :(

not urgent.

you can probably start leaving "urgent" off of every post you make.  ever hear the story of the boy who cried wolf?

I'm trying to associate the media keys (next/prev/stop/play-pause) from a nokia n96 - with a shortcut on a screen.  I get the key event on the canvas, but it's not supported natively in kuix.

what's the best way to allow these custom keys to be associated with a shortcut?

for example, the 'next' key is:

keycode: -22

keyname: Next

and I'd simply like to be able to do this:

<screen shortcuts="next=next_track|prev=prev_track">

ok, I dug into the kuix source and tried out a few things, i found out what the problem is.

in kuix 1.1.0, there's an additional catch for the new sun SDK 3.0. 

line 1044 of KuixCanvas:

} else if (currentPlatform.indexOf("SunMicrosystems") != -1 || currentPlatform.indexOf("j2me") != -1) { // SunMicrosystems = WTK 2.5.x, j2me = J2ME Platforme SDK 3.0

problem is, motorola reports the value of "j2me" for System.getProperty("microedition.platform");

that means, kuix 1.1.0 thinks that motorola phones are the new sun SDK 3.0. ouch.

I removed the check for "j2me" as the currentPlatform, and it detects the motorola just fine.  what the "real" fix is, i don't know yet, it needs some other way to detect the SDK3.0 without cutting out the motorola tests.

hey tofu, well, it seems it was sufficient in version 1.0.1 and earlier builds of KUIX, if I load the kuixdemo.jar from previous versions, it works fine, so, whatever was changed in the 1.1.0 build is the problem. and a major one in the case that motorola is waiting for me to send them a corrected version for evaluation.

ugh. bad. halp! :)

apparently kuix version 1.1.0 is wayyyy screwed up on motorola. or at least the v3xx.

I know motorola has generally different keymappings, what happened in kuix 1.1.0?

the d-pad down arrow is pressing the left soft key, and neither of the real softkeys register anything at all.

this is bad! when might there be a fix for this? I'm porting to motorola for the first release of this app (and purchase of the commercial license)

thanks!!