Resource.cpp/bin - Revision history

Lou Montana: Text replacement - "\[\[Category:BIS( |_)File( |_)Formats\]\]" to "Category:Real Virtuality File Formats"

2025-05-08T11:27:12Z

Text replacement - "\[\[Category:BIS( |_)File( |_)Formats\]\]" to "Category:Real Virtuality File Formats"

← Older revision		Revision as of 13:27, 8 May 2025
Line 11:		Line 11:


	[[Category:~~BIS_File_Formats~~]]		[[Category:Real Virtuality File Formats]]

Lou Montana: Text replacement - "{{unsupported-doc}}" to "{{Feature|UnsupportedDoc}}"

2021-02-01T13:56:56Z

Text replacement - "{{unsupported-doc}}" to "{{Feature|UnsupportedDoc}}"

← Older revision		Revision as of 15:56, 1 February 2021
Line 1:		Line 1:
	{{~~unsupported-doc~~}}		{{Feature\|UnsupportedDoc}}
	bin\resource.bin is exclusively used in OFP and contains the resource dialogs.		bin\resource.bin is exclusively used in OFP and contains the resource dialogs.

R3vo: Text replacement - " it's" to " it is"

2020-09-08T07:53:15Z

Text replacement - " it's" to " it is"

← Older revision		Revision as of 09:53, 8 September 2020
Line 8:		Line 8:
	RscDialog classes are heavily polluting. Unlike other items, there is no cfgResource class container and hence almost everything written for dialogs is a root parent. You alter or delete a root parent at your peril. Hunting for anything other than RscDialogs in the engine's post built config is noisy and time consuming. Naming and creating new dialogs is ofpec_tag critical because there is no context to refer to them, other than the root parent. If you've named your dialog "widget". You can be certain, someone else has too.		RscDialog classes are heavily polluting. Unlike other items, there is no cfgResource class container and hence almost everything written for dialogs is a root parent. You alter or delete a root parent at your peril. Hunting for anything other than RscDialogs in the engine's post built config is noisy and time consuming. Naming and creating new dialogs is ofpec_tag critical because there is no context to refer to them, other than the root parent. If you've named your dialog "widget". You can be certain, someone else has too.

	Along with the config.bin file, resource.cpp also has global defines, which, in bis, take the form of enums. These are almost the only instances of global defines in the game. This has been a clever approach, because only the engine.exe and the bin\config are tightly coupled. The nature of the engine can change, it's id's for specific dialogs(solely as an eg) can change, but all pbo's which access that reference do not require recompiles.		Along with the config.bin file, resource.cpp also has global defines, which, in bis, take the form of enums. These are almost the only instances of global defines in the game. This has been a clever approach, because only the engine.exe and the bin\config are tightly coupled. The nature of the engine can change, it is id's for specific dialogs(solely as an eg) can change, but all pbo's which access that reference do not require recompiles.


	[[Category:BIS_File_Formats]]		[[Category:BIS_File_Formats]]

Mikero at 10:33, 7 July 2011

2011-07-07T10:33:19Z

New page

{{unsupported-doc}}
bin\resource.bin is exclusively used in OFP and contains the resource dialogs.

In Arma, it has been subsumed into the standard bin\config.bin

Hindsight being that wonderful invention, it was ''probably'' better to retain it and keep dialogs out of config namespace. Certainly a little more thought was needed than simply cut and pasting the entire resource as-was.

RscDialog classes are heavily polluting. Unlike other items, there is no cfgResource class container and hence almost everything written for dialogs is a root parent. You alter or delete a root parent at your peril. Hunting for anything other than RscDialogs in the engine's post built config is noisy and time consuming. Naming and creating new dialogs is ofpec_tag critical because there is no context to refer to them, other than the root parent. If you've named your dialog "widget". You can be certain, someone else has too.

Along with the config.bin file, resource.cpp also has global defines, which, in bis, take the form of enums. These are almost the only instances of global defines in the game. This has been a clever approach, because only the engine.exe and the bin\config are tightly coupled. The nature of the engine can change, it's id's for specific dialogs(solely as an eg) can change, but all pbo's which access that reference do not require recompiles.

[[Category:BIS_File_Formats]]