Removal of components can deactivate the last component
Bug #871445 reported by
Jiri Srba
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| TAPAAL |
Fix Released
|
High
|
Kenneth Yrke Jørgensen | ||
| 2.0 |
Fix Released
|
High
|
Kenneth Yrke Jørgensen | ||
Bug Description
Open the ABP example with components. Select the first component and click three times remove component. At the end,
the last component remains but it is not activated. Now enter simulator and there is "Null Pointer Exception".
| Changed in tapaal: | |
| milestone: | 2.1 → none |
| Changed in tapaal: | |
| assignee: | nobody → Kenneth Yrke Joergensen (yrke) |
Revision history for this message
| Jiri Srba (srba) wrote | #1 |
| Changed in tapaal: | |
| status: | New → In Progress |
| Changed in tapaal: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
After some considerations, I think that the behaviour should be as follows:
The user is not allowed to remove the last activated component (even if there are more unactive ones)
and a dialog saying this should show up.