You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I want to delete Intro1, I need to shift all the subsequent numbers up. This is a pain currently because the only way to do it in Mulligan is to "Remove Numbers" then "Count" again. Because of this, it's impossible to do in one operation, or else you'd end up with suffixes 1-4 instead of 1-2 and 1-2.
We could add an operation to subtract from numbers. It would use Regex to capture number sequences, and parse them to Ints. If it failed, they'd be ignored. Otherwise they'd be replaced by the same int minus some optional parameter.
This will require a new operation, a new operation drawer, and a new binding in the MulliganRenameWindow. It should also be tested.
Test Cases
Strings have no numbers - no change
Numbers Fail to parse - this shouldn't happen on files, but in theory could happen if the operation is used on raw strings for some reason. These should be ignored.
Add 1 - adds one to all numbers
Subtract 1 - subtracts one from all numbers
Add 2 - adds two to all numbers
Subtract 2 - subtracts two from all numbers
Verify it serializes and deserializes as a Preset and when opening and closing the window.
In Sparklite we had GameStrings that were numbered, and each had a corresponding numbered Dialog Node. Ex:
Game String: Pogo_Intro1, Pogo_Intro2, Pogo_Intro3
Dialogue Nodes: Pogo_Intro1 -> Pogo_Intro2 -> Pogo_Intro3
If I want to delete Intro1, I need to shift all the subsequent numbers up. This is a pain currently because the only way to do it in Mulligan is to "Remove Numbers" then "Count" again. Because of this, it's impossible to do in one operation, or else you'd end up with suffixes 1-4 instead of 1-2 and 1-2.
We could add an operation to subtract from numbers. It would use Regex to capture number sequences, and parse them to Ints. If it failed, they'd be ignored. Otherwise they'd be replaced by the same int minus some optional parameter.
This will require a new operation, a new operation drawer, and a new binding in the MulliganRenameWindow. It should also be tested.
Test Cases
Verify it serializes and deserializes as a Preset and when opening and closing the window.
Suggested Naming for the Operation
Operation Name and Path:
Modify/Adjust Numbering
Inspector Configuration:
Add or Subtract: [int]
Relevant Files
The text was updated successfully, but these errors were encountered: