BUG FIX: Minimum and/or Maximum Acceptable Refresh Rate not saved on DisplayDevice dialog [25864]

 This article applies to:

E-Prime 3.0
E-Prime 2.0

This bug has been fixed in E-Prime 3.0.3.60 (Update 1).

 
Symptoms
The Minimum and/or Maximum Acceptable Refresh Rate properties are not saved when they are edited in the DisplayDevice Properties dialog.

 
Detail
When the default Minimum and/or Maximum Acceptable Refresh Rate property values are changed from their default settings in the DisplayDevice Properties dialog box, the user-specified values are not saved if the Refresh Rate Requested property is set to "(unspecified)".    The user-specified values are not retained and instead are replaced by the default values of 39 (Minimum) and 201 (Maximum) whenever no specific refresh rate is requested.  
 
 
Solution
Upgrade to E-Prime 3.0.3.60 or later. 

 
Workaround
There is no workaround to avoid this bug in the affected E-Prime verisons.

 
See Also:
RELEASE INFO: E-Prime 3.0 Change History [27275]