|
|
|
Re: How to create UI fields at runtime? [message #895181 is a reply to message #895132] |
Wed, 11 July 2012 21:57 |
|
Hi Dirk
As you already noticed injectFieldsInternal is called when a form gets constructed. At this time you can add or remove fields. Creating fields while a form is open is not supported so far.
What you can do is to initially create a lot of invisible fields and set the fields visible if you click on the button. Another approach would be to use a table with editable columns. Just set getConfiguredEditable to true on the column and you're done.
You're right, validateOnAnyKey only exists on string fields. If you need a key listener on an Integer field you could create a custom gui component. Just extend the existing SwtScoutIntegerField and add a key listener in the initializeSwt() method. Now you only have to register this component with the extension point org.eclipse.scout.rt.ui.swt.formfields and map it to IIntegerField.
Hope it helps.
Claudio
|
|
|
Re: How to create UI fields at runtime? [message #902441 is a reply to message #895181] |
Fri, 17 August 2012 15:11 |
Pietro Bonanno Messages: 13 Registered: July 2009 |
Junior Member |
|
|
I'm actually migrating a small app, I followed the Wiki's Notes but it keep to crash with a NPE at start.
Comparing my project with a test one created directly into 3.8, I found this difference in product's config.ini:
3.7:
osgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@start
3.8:
osgi.bundles=org.eclipse.equinox.common@2\:start,org.eclipse.update.configurator@3\:start,org.eclipse.equinox.ds@3\:start,org.eclipse.core.runtime@start
When I updated it, my app started without errors!
Now I have to solve only the lack of labels...
HTH
[Updated on: Fri, 17 August 2012 15:13] Report message to a moderator
|
|
|
|
Powered by
FUDForum. Page generated in 0.03676 seconds