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
Which results in the traits from the first storyworld being displayed once the second storyworld is open (or it throws an error when you got to the Actor editor in the second storyworld).
Open Bagatelle storyworld.
Select Editors > Actor. See the four editable traits underneath the two uneditable ones
Select File > Open. Select a storyworld where you know the traits are different (I selected my old Siboot storyworld)
Select Editors > Actor. One of two things happen:
Either an uncaught error is thrown.
Or the Actor editor is displayed and the traits from the new storyworld have been appended to the traits of the old storyworld.
The text was updated successfully, but these errors were encountered:
billmaya
changed the title
Actor editor doesn't appear to refresh correctly after opening another storyworld
Actor editor doesn't appear to refresh correctly after opening a second storyworld
Feb 1, 2019
Select Editors > Actor. Six Bagatelle traits show up
Select File > Open. Open Prom Night storyworld
Select Editors > Actor. Uncaught "Array Index Out Of Bounds" error thrown
Quit SWAT
Scenario 2
Run SWAT
Open Bagatelle storyworld
Select Editors > Actor. Six Bagatelle traits show up
File > New. Create new storyworld.
Select Editors > Actor. Six Bagatelle traits show up in list and underneath them are the five traits that should be in the new storyworld (Quiet_Chatty and Cool_Volatile are editable).
Note: When opening the new storyworld first when starting SWAT only the new storyworld's traits show up. However, if you open the new storyworld a second time the scenario 2 result will happen.
Which results in the traits from the first storyworld being displayed once the second storyworld is open (or it throws an error when you got to the Actor editor in the second storyworld).
The text was updated successfully, but these errors were encountered: