Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a boundary copying command #6

Open
leeannvidal opened this issue Nov 20, 2019 · 5 comments
Open

Add a boundary copying command #6

leeannvidal opened this issue Nov 20, 2019 · 5 comments

Comments

@leeannvidal
Copy link
Collaborator

leeannvidal commented Nov 20, 2019

Add functionality to allow to copy the boundaries of a tier to others that already have boundaries within them

@giphahne
Copy link
Owner

"copy the boundaries"
sounds like:
"copy an entire tier, but have the newly created tier have all Marks be empty"
Is that correct?

@leeannvidal
Copy link
Collaborator Author

leeannvidal commented Nov 20, 2019

I guess it would be more like "copy a tier and merge into another but have all the Marks be empty".

@giphahne
Copy link
Owner

giphahne commented Nov 20, 2019

@leeannvidal: ah, ok, so would that be (functionally) equivalent to "merge-and-mark-tiers" and then take the newly created tier and "empty" all the Marks?

Or, in other words, you need something to do the "merge" but without doing the "mark"

@leeannvidal
Copy link
Collaborator Author

@giphahne well yes and no. At the moment, one the tiers i would want it to merge into (phonological) is already kind of coded for so i would want to keep that... BUT ACTUALLY... I am thinking of the one I am working on, that would actually work for all the others because I would know ahead to just do all these commands before working on putting text into the boundaries. SO YES, that perfect, I think!

@giphahne
Copy link
Owner

If what you're going for is just to mash non-overlapping tiers together, it's just as easy to just keep whatever Marks each Tier has. It's more a logistical/process/utility discussion than a technical one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants