Bug 13099 – Add ability for Module Designer to set the default value for Module level preferences

Bug 13099 - Add ability for Module Designer to set the default value for Module level preferences


Summary:	Add ability for Module Designer to set the default value for Module level pre...

Status:	TRIAGED

Product:	VASSAL
Classification:	Applications
Component:	Editor
Version:	3.3.0-beta4
Hardware:	All All

Importance:	unspecified enhancement
Target Milestone:	---
Assigned To:	Bugs

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2020-06-16 00:12 CEST by Brent Easton
Modified:	2020-06-22 23:23 CEST (History)
CC List:	0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Brent Easton 2020-06-16 00:12:42 CEST

Module level preferences apply to an individual module and sometimes require specific settings for the module to work correctly. 

The classic example is 'Auto-report Moves' which needs to be set depending on how the Module Designer has handled reporting. Another obvious one is the Maximum Heap setting.

Default values for Module preferences are currently defined by Vassal and cannot be over-ridden by the Module Designer. So if a particular preference needs to be set, ever user who downloads the module needs to know to go in and change that preference.

Develop a method for Module Designers to record the preferred value for module level preferences.

Do not include all module level preferences as many of them (eg. Chat Colors) are really user preferences. I would include

 - All Compatibility tab preferences
 - Auto-Report moves?
 - JVM Heap Sizes