View Issue Details

IDProjectCategoryView StatusLast Update
0002596FSSCPlauncherpublic2012-11-26 05:33
ReporterYarn Assigned To 
PrioritynormalSeveritytextReproducibilityalways
Status resolvedResolutionfixed 
Platformx64OSWindows 7 
Summary0002596: SampleRate registry value replaces "Enable EFX" if present
DescriptionIn the the Audio section, there is a check box labeled "Enable EFX." If a number is entered in the Sample Rate field, that number will replace the check box's label until the SampleRate registry key is deleted.
Steps To Reproduce1. Open the Audio/Joystick tab in the launcher.
2. Enter a number into the Sample Rate field (e.g., 44100). (If you don't see it, make sure you have the most recent FSO build selected.)
3. Click OK to close the launcher and save your changes.
4. Open the launcher again and go back to the Audio/Joystick tab.
5. The number that you entered earlier will now be where the "Enable EFX" label should be.
Additional InformationThis happens with FSO Launcher 5.5g.
TagsNo tags attached.

Activities

jg18

2012-06-01 04:58

developer   ~0013623

Last edited: 2012-06-01 04:59

The problem is in line 442 in Launcher_5_5\TabSound.cpp. The coder wrote

GetDlgItem(IDC_EFX)->SetWindowText(local_port_text);

but presumably meant to write

GetDlgItem(IDC_SAMPLE_RATE)->SetWindowText(local_port_text);

Attached is a patch that makes the change.

jg18

2012-06-01 05:00

developer  

mantis_2596.patch (561 bytes)   
Index: TabSound.cpp
===================================================================
--- TabSound.cpp	(revision 8842)
+++ TabSound.cpp	(working copy)
@@ -439,7 +439,7 @@
 
 		if ( reg_get_dword(snd_reg_path, "SampleRate", &sample_rate) == true ) {
 			sprintf(local_port_text, "%d", sample_rate);
-			GetDlgItem(IDC_EFX)->SetWindowText(local_port_text);
+			GetDlgItem(IDC_SAMPLE_RATE)->SetWindowText(local_port_text);
 		}
 	} else if ( Settings::is_openal_build() ) {
 		reg_get_sz(Settings::reg_path, "SoundDeviceOAL", local_port_text, 256);
mantis_2596.patch (561 bytes)   

niffiwan

2012-11-25 08:19

developer   ~0014181

This looks like a simple fix - could a windows coder test & commit the patch from jg18?

Alternatively, if wxlauncher is ready to replace the old launcher and we're going to stop supporting it, should we close this?

Goober5000

2012-11-26 05:33

administrator   ~0014188

This is not only simple, it's trivial. Fix committed in 9377.

Issue History

Date Modified Username Field Change
2012-02-04 02:21 Yarn New Issue
2012-06-01 04:58 jg18 Note Added: 0013623
2012-06-01 04:59 jg18 Note Edited: 0013623
2012-06-01 05:00 jg18 File Added: mantis_2596.patch
2012-11-25 08:19 niffiwan Note Added: 0014181
2012-11-25 08:19 niffiwan Assigned To => niffiwan
2012-11-25 08:19 niffiwan Status new => code review
2012-11-25 08:19 niffiwan Assigned To niffiwan =>
2012-11-26 05:33 Goober5000 Note Added: 0014188
2012-11-26 05:33 Goober5000 Status code review => resolved
2012-11-26 05:33 Goober5000 Resolution open => fixed