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
It's easier to redefine which row gets changed by redefining, in this example, PrologueGeneric1.
In C2EA, to relocate a definition, one must not only change it in their definitions, but also their row in the CSV. This usually involves copying back the row from a previous version as as well overwriting a different row with your changes.
I'd like C2EA to be able to operate in a mode where one specifies the rows to change rather than inserting the table wholesale as it currently does. Then, the rows specified to change can be controlled via definitions.
As an example output, currently a table may look like (Taken from VBA2's Boss Quote Editor):
Under this proposal, one would be able to define specific rows to edit rather than writing the whole table. So if the CSV could look instead look like (if we only wanted to change one of the quotes):
One advantage of the FE:Destiny method over C2EA is that,
It's easier to redefine which row gets changed by redefining, in this example, PrologueGeneric1.
In C2EA, to relocate a definition, one must not only change it in their definitions, but also their row in the CSV. This usually involves copying back the row from a previous version as as well overwriting a different row with your changes.
I'd like C2EA to be able to operate in a mode where one specifies the rows to change rather than inserting the table wholesale as it currently does. Then, the rows specified to change can be controlled via definitions.
As an example output, currently a table may look like (Taken from VBA2's Boss Quote Editor):
Under this proposal, one would be able to define specific rows to edit rather than writing the whole table. So if the CSV could look instead look like (if we only wanted to change one of the quotes):
And the generated output would be
And MyBossQuote could be defined elsewhere.
Of course, keeping 0x2 as the entry in the first column would also be valid.
The text was updated successfully, but these errors were encountered: