Bug 358635

Comment 1 Sebastien Dubois 2011-09-23 15:02:51 EDT

The following problems are fixed:

- No more exceptions when adding anomalies
- Position is correctly set regardless from where the anomaly is created
- Class, Rank and Due date are set correctly
- The update Rule dialog shows and records the correct information

Comment 2 Jacques Bouthillier 2011-09-26 09:46:46 EDT

When testing on LINUX environment, I noticed the following:
- Select a file not in the review,
- Select a few lines from the editor and Add anomaly
- Enter a due date and use the rules set to define the class and rank
- Select OK
--> The anomaly shows in the R4E Navigator view with the proper line range, but
if you look in the R4E property view, All fields are not refresh from the previous data
Also, the "Rule ID" is never displayed.
Refresh the data by selecting the anomaly from the Navigator view, then most of the data is refreshed in the navigator view except the "Rule ID".
Now, Press "Update" to open the Anomaly details dialogue, we don't know which "Rule ID" was used
to define this anomaly. It should be highlighted.

Comment 3 Sebastien Dubois 2011-09-26 15:20:52 EDT

The follwing was done:

- Fixed small bug where RuleID was not displayed properly all the time
- Fixed bug where the properties view is not refreshed properly (not only for anomalies) when the element added to the review is done from any other view than the navigator view
- Improved Anomaly update dialog to pre-select the currently used Rule (if any)
- Removed unnecessary code that was refreshing properties