pq15274 - Under Windows, default height of a CwText  widget is different in 3.0 and 4.02. 
------------------------------------------------------------------------------------------------------------------

Affected Platforms:

	Windows NT, Windows 95


Affected Features:

	Base Smalltalk

Prerequisites:



Symptom:

	Customer is using VA4 OS/2, and has created a WindowsNotebook                 
 	with forms on it. When he puts a breakpoint in his callback                  
	code to step through it, the debugger pops up with the buttons                
 	disabled. Even when he issued a drop to selected frame, he is                 
 	not able to step thrugh the code.  Also, even when he does a                  
 	self halt, the same thing occurs. Loaded features: Comm/Trans,                
 	LOTUS NOTES, Persistence-TPF, Visualization Tools, and                        
 	Trailblazer.  Customer is also using formatted text.

Solution:

	1. Set the breakpoint at the beginning of the method that you                 
 	   want to walk through. For example:                                         
 	   *modifyVerifyAreaCode: anObject clientData: clientData                        
 	   callData:CallData                                                             
 	2. Test it so the debugger pops up (with the grayed out buttons)              
                                                                               
 	3. Place your cursor before the method name and insert a self                 
 	   halt;. For example: self halt; modifyVerifyAreaCode: anObject                 
 	   clientData: clientData callData: callData.                                    
 	4. Swipe that entire line and execute it.                                      
	5. Select the '(ExHalt) A halt has occurred.'==> from the top of              
 	   the debugger.                                                                 
 	6. Answer NO when a dialog pops up asking you to save the                     
 	   changes.                                                                      
 	7. Click INTO on the debugger. You should now be able to walk                 
 	   through your code.