hole in code found by newbee mistake

[wolf14455]

I playing hotseat/global and as Japan I was doing a gorund attack by a carrier air. The window for chosing bomber or fighter poped up, I closed it without chosing. And moved the air to the target. But it was now out of the loop I guess as it wasnt in the calculation and wasnt awailable for landing on the carrier again. But then the code found it as an overstacked air, only choise was to destroy it. When clicking done an error occured that couldnt be ignored.So reload autosave was the final result.
This happend for me some hours ago so I cant remember what autosave to send but guessed you wanted to know of the hole anyway. cheers

(got latest version and the quickfix)

[Shannon V. OKeets]

ORIGINAL: Swedewolf

I playing hotseat/global and as Japan I was doing a gorund attack by a carrier air. The window for chosing bomber or fighter poped up, I closed it without chosing. And moved the air to the target. But it was now out of the loop I guess as it wasnt in the calculation and wasnt awailable for landing on the carrier again. But then the code found it as an overstacked air, only choise was to destroy it. When clicking done an error occured that couldnt be ignored.So reload autosave was the final result.
This happend for me some hours ago so I cant remember what autosave to send but guessed you wanted to know of the hole anyway. cheers

(got latest version and the quickfix)

Okay. You might have used the little X in the upper right corner to close the form since the OK Done button should have been disabled.

EDIT: No, my above statement isn't correct. This is a bug reported by others where a carrier air unit flying as a fighter (the assumed role when you don't choose a role) sometimes gets "left behind" and causes an overstacked error in a later phase.

[wolf14455]

Good its captured. Trying to minimize my newbee actions [:D]
cheers