
|
If you were logged in you would be able to see more operations.
|
|
|
Osmorc
Created: 06 Apr 08 21:23
Updated: 10 Sep 09 14:47
|
|
| Component/s: |
None
|
| Affects Version/s: |
0.4.0
|
| Fix Version/s: |
0.5.0
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
Currently the creation and deletion of framework instance libraries is somehow delicate. Some constellation like the creation and subsequent deletion of the same libraries don't work or don't work as expected. The reason for this is that the Settings-Editor accumulates all changes to framework instance libraries and commits them when the Apply or OK buttons are pressed.
A different approach may be helpful here: Create or delete the libraries as soon as a framework instance is added or removed. When the user presses the cancel button, recreate libraries that have been deleted and delete libraries that have been created in this invocation of the Settings editor.
This approach has one negligible side effect: Removing a framework instance and then canceling the change has a reloading effect on the framework instance.
|
|
Description
|
Currently the creation and deletion of framework instance libraries is somehow delicate. Some constellation like the creation and subsequent deletion of the same libraries don't work or don't work as expected. The reason for this is that the Settings-Editor accumulates all changes to framework instance libraries and commits them when the Apply or OK buttons are pressed.
A different approach may be helpful here: Create or delete the libraries as soon as a framework instance is added or removed. When the user presses the cancel button, recreate libraries that have been deleted and delete libraries that have been created in this invocation of the Settings editor.
This approach has one negligible side effect: Removing a framework instance and then canceling the change has a reloading effect on the framework instance. |
Show » |
| There are no comments yet on this issue.
|
|