Bugzilla – Full Text Bug Listing
| Summary: | Analysis Result in Properties view not drawn correctly | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Yasuhisa Gotoh <gotohy> | ||||
| Component: | TPTP | Assignee: | Alex Nan <apnan> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P1 | CC: | jkubasta, labadie, rohit.shetty | ||||
| Version: | unspecified | Keywords: | plan | ||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
This problem seems to be caused by the org.eclipse.ui.forms.widgets.FormText widget itself. When I replaced the FormText widget with the org.eclipse.swt.widgets.Text widget, the analysis result data was drawn correctly in the Properties view. This is required from the AC perspective. Fixed. Verified with the 4.5 RC3 driver. Closing. |
Created attachment 77619 [details] screenshot When a long dashed line with minus character like "--------------------------------------------------------------------" is contained in texts of symptom definitions in a symptom v0.1 catalog, the content of Analysis Result in the Properties view is not drawn correctly. See the attached screenshot for details. Driver: TPTP-4.4.1-200708280100 Steps to reproduce: 1. Create a symptom v0.1 catalog. 2. Open the catalog in the Symptom Editor and add a new symptom definition with a new solution and a new directive. 3. Set the following text in the symptom description field. Symptom_1 -------------------------------------------------------------------- 4. Set the following text in the solution description field. Solution_1 -------------------------------------------------------------------- 5. Set the following text in the directive description field. Directive_1 -------------------------------------------------------------------- 6. Set an appropriate match pattern for a log file in the match pattern field of the symptom definition and save the symptom catalog. 7. Import a target log file and the created symptom catalog, then run "Analyze All" from the Log view. 8. Open the Properties view and show the Analysis Result by selecting a matched log record in the Log view. 9. The dashed line corrupts the upper line as shown in the attached screenshot.