Files
firestorm/Gameleap/code/mw4/Tools/autoconfig
CydandClaude Fable 5 2f17631081 FS507D asset recovery, ConLobby V5.0.7Df promotion, mechlab New-Mech crash fix
FS507D_20161015 release analysis wrap-up (drop itself is gitignored; art-review
folder kept local for review):
- Recovered the only assets our tree lacked: 13 hsh HUD/radar/mech bmps and the
  two 5.07D lobby decals (decal_46/47.tga, extracted from release props.mw4 via
  a ported gos_LZDecompress).
- ResourceImagePool.cpp: missing-texture placeholder is now LAB_ONLY (editor
  keeps degraded mode); Release restores the original fatal STOP. Release +
  Profile rebuilt, 0 errors.

Console script reconciled:
- ConLobby.script.new ("BattleTech Console V5.0.7Df", newest revision anywhere)
  promoted to Content\ShellScripts\ConLobby.script; .new removed; stale loose
  deploy copy removed. Verified in-game (console title shows V5.0.7Df).
- Corrected CLAUDE.md: the release never "renamed" the console to
  ComputerPlayer.script -- the resource packer stores script contents under
  alphabetically skewed entry names (runtime resolves the same pairing).
  Packer quirks documented (stale entry carry-forward on incremental builds,
  name/content skew in directory sweeps).

Mechlab bug fix (first FireStorm bug hunt):
- New-Mech dialog showed blank rows for Wolfhound/Zeus and crashed (KERNELBASE
  read AV) when creating a Zeus. Root cause: newmech in chassis.script created
  its Type droplist without setting $$m_listBoxSize$$, so capacity defaulted to
  60 while 65 chassis were written in -- OOB script-array writes. Fixed by
  sizing the list from $$m_chassisCount$$. Latent stock-MW4 bug armed when the
  FireStorm roster passed 60 chassis. Verified: Zeus variant creates cleanly.

props.mw4 fully repacked (decals + promoted console + mechlab fix, junk
.new/.org entries gone); game deploy refreshed at MW4\. Gitignore: FS507D drop
and player-created MW4\Resource\Variants.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-02 13:04:45 -05:00
..

========================================================================

       MICROSOFT FOUNDATION CLASS LIBRARY : autoconfig

========================================================================





AppWizard has created this autoconfig application for you.  This application

not only demonstrates the basics of using the Microsoft Foundation classes

but is also a starting point for writing your application.



This file contains a summary of what you will find in each of the files that

make up your autoconfig application.



autoconfig.dsp

    This file (the project file) contains information at the project level and

    is used to build a single project or subproject. Other users can share the

    project (.dsp) file, but they should export the makefiles locally.



autoconfig.h

    This is the main header file for the application.  It includes other

    project specific headers (including Resource.h) and declares the

    CAutoconfigApp application class.



autoconfig.cpp

    This is the main application source file that contains the application

    class CAutoconfigApp.



autoconfig.rc

    This is a listing of all of the Microsoft Windows resources that the

    program uses.  It includes the icons, bitmaps, and cursors that are stored

    in the RES subdirectory.  This file can be directly edited in Microsoft

	Visual C++.



autoconfig.clw

    This file contains information used by ClassWizard to edit existing

    classes or add new classes.  ClassWizard also uses this file to store

    information needed to create and edit message maps and dialog data

    maps and to create prototype member functions.



res\autoconfig.ico

    This is an icon file, which is used as the application's icon.  This

    icon is included by the main resource file autoconfig.rc.



res\autoconfig.rc2

    This file contains resources that are not edited by Microsoft 

	Visual C++.  You should place all resources not editable by

	the resource editor in this file.









/////////////////////////////////////////////////////////////////////////////



AppWizard creates one dialog class:



autoconfigDlg.h, autoconfigDlg.cpp - the dialog

    These files contain your CAutoconfigDlg class.  This class defines

    the behavior of your application's main dialog.  The dialog's

    template is in autoconfig.rc, which can be edited in Microsoft

	Visual C++.





/////////////////////////////////////////////////////////////////////////////

Other standard files:



StdAfx.h, StdAfx.cpp

    These files are used to build a precompiled header (PCH) file

    named autoconfig.pch and a precompiled types file named StdAfx.obj.



Resource.h

    This is the standard header file, which defines new resource IDs.

    Microsoft Visual C++ reads and updates this file.



/////////////////////////////////////////////////////////////////////////////

Other notes:



AppWizard uses "TODO:" to indicate parts of the source code you

should add to or customize.



If your application uses MFC in a shared DLL, and your application is 

in a language other than the operating system's current language, you

will need to copy the corresponding localized resources MFC42XXX.DLL

from the Microsoft Visual C++ CD-ROM onto the system or system32 directory,

and rename it to be MFCLOC.DLL.  ("XXX" stands for the language abbreviation.

For example, MFC42DEU.DLL contains resources translated to German.)  If you

don't do this, some of the UI elements of your application will remain in the

language of the operating system.



/////////////////////////////////////////////////////////////////////////////