Enable selection of Radio buttons and Checkboxes
Status: Alpha
Brought to you by:
raner
Hi,
I want to create projects automatically. While using MyEclipse, I need to select some radio buttons and sometimes checkboxes, which are listed in a listbox.
At the moment, I think, I can only click a button.
Thanks and kind regards
Joachim
Logged In: YES
user_id=738867
Originator: NO
Hello Joachim,
I assume you are talking about situations like the "Export Preferences" or "Export Deployable Features" dialog. Indeed, check boxes and radio buttons that are nested inside lists or tabs cannot be operated by Escripts yet. I will add support for this feature as soon as I get a chance, after I'm done with the features I'm currently working on.
In the meantime, I can offer you two possible work-arounds (which might or might not work for your particular problem):
(1) if the elements that you need to select in the list happen to be resources from the workspace you might want to try using a nested <selection> element. Most resource-related wizards, actions, and commands pick up the current workspace selection as their initial default selection. You can find some examples in the documentation:
- http://escripts.sourceforge.net/index.php/Escripts_Documentation#Commands
- http://escripts.sourceforge.net/index.php/Escripts_Documentation#Selections
- http://escripts.sourceforge.net/index.php/Escripts_Documentation#Example_Scripts
(2) instead of adjusting the settings by clicking the UI elements, you can directly change the IDialogSettings of a wizard using a nested <settings> element. This feature is not documented yet but you can see an example at http://escripts.svn.sourceforge.net/viewvc/escripts/trunk/net.sf.escripts.tests/src/net/sf/escripts/tests/SettingsElement.xml?revision=69&view=markup or refer to the source code at http://escripts.svn.sourceforge.net/viewvc/escripts/trunk/net.sf.escripts/src/net/sf/escripts/elements/SettingsElement.java?revision=69&view=markup
The latter option will require at least revision 69 of the code, which means you'll have to build Escripts by yourself (the latest release is only revision 59). That, however, shouldn't be all that hard. Basically, importing the sources into your Eclipse workspace and exporting a deployable feature should do the trick.
Also, you might have to dig through Eclipse source code a little bit to find out the property keys of the settings that you want to change.
HTH,
Mirko
P.S.: You might want to create a SourceForge account for filing and commenting on feature requests. You filed this request anonymously, so I can't contact you directly.