Messages by Bo

I'm please to inform you that you can download a ready to run NetBeans project directly from Subversion.

More informations on this page.

Yes, bug fixed : http://www.kalmeo.org/forum/topic/189/secondmenu-removing-menuitem/1#post727

Thanks to have pointed this bug.

This bug was fixed on SVN.

And a new feature was added to change dynamicly menus at runtime : Kuix.loadMenuContent(Menu, String, DataProvider).

To change ScreenFirstMenu content, simply do something like this :

Kuix.loadMenuContent(myScreen.getFirstMenu, "myMenu.xml", null);

Yes, but you need to know that loadCss(...) method append new styles to registred styles and in this case old defined styles stay available. That's why it could be a lillte confuse to load a widget tree from xml file and imagine that the new css definition wil be applied only to those widgets ...

It seems to be more an emulator problem, because it doesn't clear loaded classes when the application is closed. And in this case all static classes became a real problem ... because they wouldn't be reinitialized.

This wouldn't appear on real phone.

Yes, thanks, but as I mentionned in my email answer we don't have any problem with the installation of your compiled version on our test phones (without testing it on a N72)

In the past the choice was done to prefer a global Tab navigation than moving focus to a tabButton to navigate through them. In this case the ONLY way to change tab is to bind a Key for forward navigation and an other for backward navigation. The most evident choice was to use LEFT and RIGHT keys.

This choice is our for two reasons :

• Keep the current focus widget en each tab event if the tab is hidden.
• have an easy tab navigation because it's an important thing on mobile UI
  

Because of this choice, we need to observe some rules :

• Do not propose an horizontal focus navigation in a tabItem
• Do not use tab navigation keys for something else.

Then How to control tab navigation ?

With 1.0, you can't. We actualy thinking on adding the possibility to change the default tab key navigation by defining two attributes on the TabFolder ... but I think it's not enough for your problem. But event if you control the tab navigation how could you choice between focus navigation and tab navigation ?

For the moment, this is not planed for the next release.

If I understand, you would like to "hide" tab navigation key when the focus is on tabItem content ?

Or you want to be able to configure tab navigation key to Up and Down ?

Text widget never wrap its text content. But to do this, you need to replace Text by TextArea.

Somme question to understand :

• Does this exception occure on first start ?
• Does this exception occure only on the simulator ?
• Does this exception occure always after you close and restart the application ?
• When you close the application, do you close the simulator ?
• What IDE / WTK combination do you use ?

The strange thing is that in theory if you close the application, the me mory is free.

As you can see, a top input as appear on top of the forum.

> The text is too long that some of the content are sliced. Is there a way to wrap it to the next line.

Yes, use a TextArena

> OutOfMemory

It seems that the error occure on application startup (... MIDletProxy.startApp(MIDletProxy.java:44) ..), is it true ? When you say that you close the application does that meen that the application is totaly closed ?

scrollbar:visible:true doesn't exist you need to use the ScrollPane attribute showScrollBar="true". Take a look at the Widget Reference page.

Else, ScrollPane, because of its unconsistant content doesn't have any content size. In this case, it doesn't make sens to put a ScrollPane in an inlineLayout.

ScrollPane need to be placed in widget with auto spaced layout like GridLayout, BorderLayout (only on center). Else you can specify manualy the min size of your ScrollPane widget with the min-size style property

By default the screen layout is GridLayout(1,1) which is compatible with ScrollPane, and ScrollPane scrollBar is visible why not simply use this syntax ?

<screen>

<scrollpane>

<!-- here your screen content -->

</scrollpane>

</screen>

> how can i open a browser from kuix application. I know that from a midlet you can use platformRequest() method to open browser. Can we do the same in kuix and will it work?

Yes

> how can we do text wrapping in text field?

It is not implemented for the moment, but planned for the next release.

> ... when you are using @{..} properties to remove the link between dataprovider and the widget. Am I right ? if yes what should I do to overcome this error ? If i am wrong what else should i do?

Yes, if you use @{...} properties, you need to invoke the cleanUp() method on widgets when you no longer use them. The best way would be to invoke this cleanUp method on a screen when you remove it (only if some of its widgets has @{...} properties).