- Create new MIDP project
- Open project properties
- DefaultCldcPhone1 is selected and all Optional Packages are chosen
- Select DefaultCldcJtwiPhone1 it has only to optional packages
- Select DefaultCldcPhone1 again, now it has only two optional packages chosen.

When new project is created it is configured to use all available optional packages for selected emulator. If you change the emulator in project properties three cases can happen:
1. new emulator supports all optional packages defined in the project. In this case all optinal packages stay selected.
2. new emulator does not support some of defined optional packages. In this case these optional packages are removed from project properties.
3. new emulator supports more optional packages than old emulator. In this case project properties keep the list of previously selected optional packages and the rest of optional packages stays unselected.


But implementation for this feature is not completely correct:
"Change emulator" means to choose it in a list and confirm this by closing project's properties window.
If user wants just look in a list of supported devices and check their jsr's, he shouldn't be forced to check all jsr back after looking on DefaultCldcJtwiPhone.

So selection of optional packages should be saved only after closing project's properties.