[Fixed] Editing the Scenario description locks up program

[BeirutDude]

This has cropped up a few times. In the current scenario I am working on trying to edit the scenario description to correct a mistake is locking up the program.

[Dimitris]

Is this happening to you with any scenario or on a specific scenario? If the latter, can we see it?

[BeirutDude]

Was still doing some edits. Took me five tries to get in there (edit the file). What finally seemed to break it loose was editing the Side Briefing and then opening the Scenario Briefing. Hope that helps. The Turkish scenario was the one I needed to edit, but happened with both sides.

Now I...

1. Edit my briefings in Word (for spell check)
2. Copy to Wordpad and save without formatting to delete any special characters
3. Reopen the briefing in Wordpad to ensure formatting is gone.
4. paste in CMO
5. Edit Bold/etc. in CMO.

[Rory Noonan]

Logged for investigation.

0013777

[KnightHawk75]

Got frustrated after losing hours of work yet again to this found what is hopefully helpful info for this.

What's happening it seems is the dialog is is being loaded behind CMO main window and getting modality or focus and not being brought to the forefront, or alternatively modality is lost on the main window but the new one isn't being drawn\spawned yet till the minimize-workaround mentioned next happens. The only way (and I can consistently do this as a workaround now that I found it) is to via task manager (or winkey+downarrow) highlight the CMO app and specifically trigger a 'minimize' from there, then the dialog window instantly loads\shows up center screen (and on taskbar but only after you select it) where you can make your edits or cancel.

I don't know what it's doing\checking before showing the dialog but whatever it is seems to have different results depending on save\scenario beyond the contents of the text. This also happens with: Game\Side briefing, Game\Scenario Description, and Editor\ Edit side briefing - HOWEVER in those cases the game itself doesn't lockup-lose modality so you can minimize normally and then the window will show up onscreen\on taskbar.

I can reproduce this in CMO 139.2 and 141.2 100% of the time on my system with the attached scenes on my system, one sample is a save of the relative end state of playing a modded fiery cross reef, and two others are just some random things I was playing around with and those two only include a couple dozen units. Both show the behavior 100% of the time for me after being loaded, where most older community and included scenes I tested don't show the behavior, nor does a brand new scenario with like 2 sides and a couple generic modded units.

BTW I've also seen something similar happen with the shift-f1 manual fire screen after using it a hundred+ times after like 12+ real hours into playing a session where the screen is gone and you should be selecting a unit\target but you can't select any unit or shift-f1 to bring it up again. It's probably a separate issue I just mention it because funny enough the solution when that bug happens with shift-f1 is usually to trigger the scenario description edit dialog, which for whatever reason seems to reset the cursor or cancel out of the manual fire process that gets fubar'd.

@BeirutDude - Try the forced minimize work around, let me know if it works for you and it's not just some freak fix applying only to me.

[BeirutDude]

So I have looked for it behind the main screen without success and opening Task Manager actually crashes the program when it happens to me. I have learned to NOT open a description/editor window until everything has been saved but yes have lost hours worth of work myself (that's how I learned, the had way!). In CMO I have (re)learned to "save early, save often!"

[SteveMcClaire]

This issue should be fixed in the next update.

[AlexinCT]

I have found that if you try to open the scenario description when at high altitude in the map the screen locks. If you scroll down to a very low altitude (and even have a screen with just open terrain), the issue doesn't happen...