Final Cleanup (Savage) - Revision history

Rob: /* Sample Timing Problem */

2009-02-21T00:08:42Z

Sample Timing Problem

← Older revision		Revision as of 00:08, 21 February 2009
Line 56:		Line 56:

	===Sample Timing Problem===		===Sample Timing Problem===

			After a bit of poking around, there is one problem we can uncover. If we change the default value of attributes from two to zero, we'll then rely on the proper bounding logic to be applied that keeps the value between two and six. However, making that change reveals a problem that we need to resolve.

	When we create a new character, the number of attribute points is being displayed as "-12 of 5" above the table of attributes. The moment that we make any change at all to the character, everything behaves correctly. We obviously have a timing problem.		When we create a new character, the number of attribute points is being displayed as "-12 of 5" above the table of attributes. The moment that we make any change at all to the character, everything behaves correctly. We obviously have a timing problem.
Line 80:		Line 82:

	The only other use of the "Trait" component is with derived traits. Since there is no resource being tallied for derived traits, there are no other places where this problem could be lurking.		The only other use of the "Trait" component is with derived traits. Since there is no resource being tallied for derived traits, there are no other places where this problem could be lurking.

			Once the bug is resolved, we can restore the original default value back to two.

	===Rank and XP Shown for Creatures===		===Rank and XP Shown for Creatures===

Rob: /* New Characters Report Wrong Attribute Points */

2009-02-20T23:53:13Z

New Characters Report Wrong Attribute Points

← Older revision		Revision as of 23:53, 20 February 2009
Line 47:		Line 47:
	{{note}}If our game system did not use the advancements mechanism, we could also delete the data files specific to advancements and all the associated references.		{{note}}If our game system did not use the advancements mechanism, we could also delete the data files specific to advancements and all the associated references.

	===~~New Characters Report Wrong Attribute Points~~===		===Identifying Timing Problems===

			One of the details we should verify during cleanup is whether we have any timing problems within our data files. Unless we did an exhaustive job of establishing and maintaining timing dependencies during development (we didn't), it's quite likely that we're going to have at least one or two holes in our logic. These holes might not even be visible right now, but future changes or user extensions could expose them.

			The best thing we could do right now is to go through and establish thorough timing dependency relationships everywhere. Any task that relies on other values can be assigned a named "after" timing dependency on the scripts that calculate those values. Alternately, the scripts that calculate can be assigned a named "before" dependency on the script that uses the value. That's going to entail a healthy amount of work, so it's probably not a practical solution.

			What we can do instead is some spot testing to see if we can uncover problems. Whenever we do uncover a problem, we can take the time to add the appropriate timing dependency relationships to the involved tasks. This won't be perfect, but it will be much faster and will ensure that we begin improving our use of enforced timing dependency relationships.

			===Sample Timing Problem===

	When we create a new character, the number of attribute points is being displayed as "-12 of 5" above the table of attributes. The moment that we make any change at all to the character, everything behaves correctly. We obviously have a timing problem.		When we create a new character, the number of attribute points is being displayed as "-12 of 5" above the table of attributes. The moment that we make any change at all to the character, everything behaves correctly. We obviously have a timing problem.

Rob: /* Tailor Display Widths */

2009-02-12T00:53:27Z

Tailor Display Widths

← Older revision		Revision as of 00:53, 12 February 2009
Line 200:		Line 200:
	*Widen the "adjust" portal within the "abAttrPick" template on the "Basics" tab by 10 pixels so that a bonus of "+10" (for creatures) doesn't get clipped. This requires also changing the alignment gaps of both the "adjust" and "value" portals to "-8".		*Widen the "adjust" portal within the "abAttrPick" template on the "Basics" tab by 10 pixels so that a bonus of "+10" (for creatures) doesn't get clipped. This requires also changing the alignment gaps of both the "adjust" and "value" portals to "-8".
	*Widen the "adjust" portal within the "skPick" template on the "Skills" tab by 5 pixels so that a bonus of "+10" doesn't get clipped. This requires also changing the alignment gap of the "adjust" portal to "6".		*Widen the "adjust" portal within the "skPick" template on the "Skills" tab by 5 pixels so that a bonus of "+10" doesn't get clipped. This requires also changing the alignment gap of the "adjust" portal to "6".
			*Widen the "attack" portal within the "smWeapon" template on the "Armory" summary panel by 10 pixels to show attacks better than "d12" (e.g. "d12+1")

	===Consistent Terminology with Rulebook===		===Consistent Terminology with Rulebook===

Rob: /* Tailor Display Widths */

2009-02-11T23:22:11Z

Tailor Display Widths

← Older revision		Revision as of 23:22, 11 February 2009
Line 189:		Line 189:
	*Edges table - increase to 350		*Edges table - increase to 350
	*Hindrances table - increase to 350		*Hindrances table - increase to 350
			*Abilities table - increase to 350
	*Race chooser - increase to 350		*Race chooser - increase to 350
	*Creature chooser - increase to 350		*Creature chooser - increase to 350

Rob: /* Tailor Display Widths */

2009-02-11T06:43:47Z

Tailor Display Widths

← Older revision		Revision as of 06:43, 11 February 2009
Line 197:		Line 197:
	*Widen the "arWpnThing" template on the "Armory" tab by 25 pixels		*Widen the "arWpnThing" template on the "Armory" tab by 25 pixels
	*Widen the "arDefThing" template on the "Armory" tab by 25 pixels and shift the defensive value over the same 25 pixels		*Widen the "arDefThing" template on the "Armory" tab by 25 pixels and shift the defensive value over the same 25 pixels
			*Widen the "adjust" portal within the "abAttrPick" template on the "Basics" tab by 10 pixels so that a bonus of "+10" (for creatures) doesn't get clipped. This requires also changing the alignment gaps of both the "adjust" and "value" portals to "-8".
			*Widen the "adjust" portal within the "skPick" template on the "Skills" tab by 5 pixels so that a bonus of "+10" doesn't get clipped. This requires also changing the alignment gap of the "adjust" portal to "6".

	===Consistent Terminology with Rulebook===		===Consistent Terminology with Rulebook===

Rob: /* Tailor Display Widths */

2009-02-10T08:04:34Z

Tailor Display Widths

← Older revision		Revision as of 08:04, 10 February 2009
Line 195:		Line 195:

	*Widen the "stRace" chooser on the static form by 10 pixels to accommodate all races		*Widen the "stRace" chooser on the static form by 10 pixels to accommodate all races
			*Widen the "arWpnThing" template on the "Armory" tab by 25 pixels
			*Widen the "arDefThing" template on the "Armory" tab by 25 pixels and shift the defensive value over the same 25 pixels

	===Consistent Terminology with Rulebook===		===Consistent Terminology with Rulebook===

Rob at 14:35, 9 February 2009

2009-02-09T14:35:37Z

Show changes

Rob: /* Tailoring Widths */

2009-02-09T14:30:15Z

Tailoring Widths

← Older revision		Revision as of 14:30, 9 February 2009
Line 182:		Line 182:
	</pre>		</pre>

	===~~Tailoring~~ Widths===		===Tailor Display Widths===

	There are a number of dynamic tables that present choices with lengthy descriptions. In order to better accommodate these descriptions, we need to increase the space afforded for showing those descriptions. This is controlled through the "descwidth" attribute on the table portals. The following changes should be made.		There are a number of dynamic tables that present choices with lengthy descriptions. In order to better accommodate these descriptions, we need to increase the space afforded for showing those descriptions. This is controlled through the "descwidth" attribute on the table portals. The following changes should be made.

Rob: /* Widen Description Widths */

2009-02-09T14:27:20Z

Widen Description Widths

← Older revision		Revision as of 14:27, 9 February 2009
Line 182:		Line 182:
	</pre>		</pre>

	===~~Widen Description~~ Widths===		===Tailoring Widths===

	There are a number of dynamic tables that present choices with lengthy descriptions. In order to better accommodate these descriptions, we need to increase the space afforded for showing those descriptions. This is controlled through the "descwidth" attribute on the table portals. The following changes should be made.		There are a number of dynamic tables that present choices with lengthy descriptions. In order to better accommodate these descriptions, we need to increase the space afforded for showing those descriptions. This is controlled through the "descwidth" attribute on the table portals. The following changes should be made.
Line 191:		Line 191:
	*Race chooser - increase to 350		*Race chooser - increase to 350
	*Creature chooser - increase to 350		*Creature chooser - increase to 350

			There are also a small number of other places where we can tweak the widths to better accommodate the information being displayed. These include the following:

			*Widen the "stRace" chooser on the static form by 10 pixels to accommodate all races

	===Consistent Terminology with Rulebook===		===Consistent Terminology with Rulebook===

Rob: /* Widen Description Widths */

2009-02-09T14:10:12Z

Widen Description Widths

← Older revision		Revision as of 14:10, 9 February 2009
Line 189:		Line 189:
	*Edges table - increase to 350		*Edges table - increase to 350
	*Hindrances table - increase to 350		*Hindrances table - increase to 350
			*Race chooser - increase to 350
			*Creature chooser - increase to 350

	===Consistent Terminology with Rulebook===		===Consistent Terminology with Rulebook===