Bug 85718

Summary: Run Tests dialog Executables pane checklist drawing problem
Product: [Retired] eCos Reporter: John Dallaway <jld>
Component: ConfigToolAssignee: John Dallaway <jld>
Status: CLOSED CURRENTRELEASE QA Contact: John Dallaway <jld>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0 beta 1CC: jifl-bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-04-04 13:02:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description John Dallaway 2003-03-06 13:43:46 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3; Linux)

Description of problem:
The checklist in the Executables pane of the Run Tests dialog does not get drawn properly on Win2k and WinXP hosts. The problem is less marked on Win98SE. Scrolling very slowly will force a redraw and allow you to see the content of the checklist. configtool on Linux is not affected.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Build eCos tests
2. Invoke the Run Tests dialog
3.
    

Actual Results:  Typically only the first executable is seen in the checklist. The others are there but have not been drawn correctly. Scrolling rapidly causes all sorts of mis-drawn content to appear.

Expected Results:  A full list of executables should appear.

Additional info:

The checklist uses wxCheckListBox which requires wxUSE_OWNER_DRAWN support in the wxWindows library. Probably a bug in wxWindows.

eCos Configuration Tool 2.12.net (eCos 2.0b1) built using Visual C++.

Comment 1 John Dallaway 2003-04-03 15:54:54 UTC
Similar issues observed under Win98 have been resolved by building the 
configtool against wxWindows 2.4.0. I need to verify that the issues are also 
resolved on Win2k/WinXP. 

Comment 2 John Dallaway 2003-04-04 13:02:37 UTC
Fixed by building against wxWindows 2.4.0.