Rapid changes in FSO binary selection can cause binary changed event in the middle of flag file processing

[IssMneur]

From [email protected] on June 16, 2012 10:20:23

What steps will reproduce the problem? 1. Start wxL (debug build)
2. Switch to a profile with a valid root folder/FSO binary.
2. Rapidly change the selected binary back and forth among the binaries listed on the basic settings page (works best on Windows) What is the expected output? What do you see instead? Expected output is for no asserts or checks to fail. Instead, the wxCHECK_RET at the start of FlagListManager::OnBinaryChanged() fails, because it receives a binary change event in the middle of flag file processing for a previously selected binary.

Original issue: http://code.google.com/p/wxlauncher/issues/detail?id=88

[IssMneur]

From [email protected] on June 23, 2012 14:55:53

Owner: [email protected]

[IssMneur]

From [email protected] on June 25, 2012 23:06:52

The resolution to this problem is going to require more invasive changes than what can be justified in a point release (or at least such such short notice).

Labels: -Milestone-Release0.9.1 Milestone-Release0.10.0