When a user goes to build or rebuild a story, Twine opens the save dialogue at the location where any file was last saved - not at the place where the currently open file was last built/rebuilt. Twine should remember save locations on a file-specific basis. (I know that the 'View last build' function can overcome this second limitation. But this is almost a workaround rather than fixing the core problem.
A key question for solving this build/rebuild location problem is whether the location to be remembered should be stored in the Windows registry or in a special memory file on the one hand, or whether on the other hand the information should be stored in the .TWS file itself. The problem with storing the information in the .TWS file is that if that file is shared with another user the location information will be obsolete.
When a user goes to build or rebuild a story, Twine opens the save dialogue at the location where any file was last saved - not at the place where the currently open file was last built/rebuilt. Twine should remember save locations on a file-specific basis. (I know that the 'View last build' function can overcome this second limitation. But this is almost a workaround rather than fixing the core problem.
A key question for solving this build/rebuild location problem is whether the location to be remembered should be stored in the Windows registry or in a special memory file on the one hand, or whether on the other hand the information should be stored in the .TWS file itself. The problem with storing the information in the .TWS file is that if that file is shared with another user the location information will be obsolete.