Store twine passage position information in modified .twee file #160
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
data. Added preference to control whether to include twine position data in twee exports.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While searching for information to facilitate editing in an external program without loosing the graph I came across this conversations:
http://twinery.org/forum/index.php?topic=1403.0
which pretty much said what I was looking for was not currently implemented. However it did give me enough information to suggest it was very doable. So I did. I don't know if this is of use to anyone else or just myself and being new to the twine community I wasn't sure if this is something that is generally wanted or if there is some other plan to handle the issue.
I created a new preference. Unfortunately I couldn't seem to get it to default to False. If someone can point me to what I'm missing I'll fix it.
This patch creates a new section in a passage after the tags containing key value pairs. At present it handles 'twine-pos-x' and 'twine-pos-y'. If you do export to twee (while the pref is set) it will populate those values in the twee file. Import from twee will similarly read them and place the passage widgets according to those values.
Standard twee files continue to work and if the pref is set to false standard twee files can still be generated.