Latest messages

33 topics, 101 messages
Kuix bug report » Not sure if this is a bug...

Yes, push frame do not put it on top. In some case it is preferable to assume the presence of a frame by repuching it without change its position if it was already present. It's right that at present there's no way to put a frame on top. But we can imagine adding de putFrameOnTop(frame) method on FrameHandler.

Ok, I understand the remove problem. I think the putFrameOnTop method could solve it no ?

Kuix bug report » Not sure if this is a bug...

If I push a frame into the stack that already is in the stack then shouldn't it go on top ? What I'm trying to achieve (among other things) is a way to show a frame from multiple different screens. And when I remove that frame, I want to go back to the frame from which I showed it. So basically some kind of push/pop stack operations.

Kuix bug report » Not sure if this is a bug...

At present, FrameHandler.pushFrame(frame) do not 'repush' a frame if it was already present in the stack, and the frame stay at its position in the stack. Is that the origin of your interrogation ?

Do you want to put your frame on top of all ? Else you can remove the frame en push it again and it will be on top.

Kuix bug report » Not sure if this is a bug...

I'm not sure whether this is a bug or by design. But the way the FrameHandler handles the Frame stack is a bit strange. If I push a frame on the stack and then later in another screen I push that same screen on the stack again, it doesn't get activated. I think that the stack should work so that if I push a frame on it, it should automatically go on top. Or am I missing something ?

Kuix bug report » The isFullscreen() method of KuixMIDlet is not used

Ho right, it was a mistake. Thanks for reporting the bug.

I tired to return false in isFullScreen() and it works fine, on WTK emulator and a Nokia phone.

Kuix bug report » The isFullscreen() method of KuixMIDlet is not used

Oh... There seems to be some other troubles with setting the full screen to false also. I tried applying the above fix to KuixMIDlet, but the app is still displayed fullscreen. Don't know what is going on.

Kuix bug report » The isFullscreen() method of KuixMIDlet is not used

The isFullscreen() - method is never called when creating the Canvas. The creation of the KuixCanvas in KuixMIDlet.startApp should be:

canvas = new KuixCanvas(this, isFullscreen());

 

Kuix bug report » Desktop bg-color not right

Hi, you just click one time on the left menu with one button ?

Else, this bug could be produce by using the left and right button of the mouse at the same time. After that the emulator repeat the pressed event all the time. That's why it could blink...

Kuix bug report » Desktop bg-color not right

Hi.

i depolyed KuixDemo application in sun wtk's emulator,

then in left menu, when i just clicked menu, it started to shake, and popupmen started to blink...

i think that there is bug in kuixdemo appln

Please try kuixdemo application, i have used eclipse ide

 

Kuix bug report » Desktop bg-color not right
Hi, in the demo, the background color is realy light. Maybe the color is not visible on your E51 or not in the color palette of your phone. Does the problem persist if you change the bg-color by red ?
Kuix bug report » Desktop bg-color not right
Hi, I just discovered your library yesterday, and I've been testing a bit. Seems to be an excellent framework. One thing I noticed right away was that (even with your own demo application) the bg-color attribute in the css doesn't seem to work at least with Nokia E51. In my emulator (wtk default color phone) the color is correct, but once I try it on my phone, the background stays white no matter what the desktop bg-color is set to.