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

"global replace" merge mode considered harmful #2

Open
mikeroberts3000 opened this issue Sep 25, 2013 · 0 comments
Open

"global replace" merge mode considered harmful #2

mikeroberts3000 opened this issue Sep 25, 2013 · 0 comments

Comments

@mikeroberts3000
Copy link

Surprisingly, feedback received from our group of Summer 2013 interns suggests that the "global replace" merge mode is counter-productive. The interns simply did not find this merge mode useful. The interns went so far as to suggest that we should remove the "global replace" merge mode from Mojo to remove the possibility that an inexperienced user would make the mistake of using it.

Since "global replace" is the only merge mode that doesn't touch pixel data (i.e., both other merge modes touch pixel data), this is an issue that warrants rethinking the data structures used to manage merging.

To work around this issue, the interns encouraged each other to never use the merge tool, and instead use the merging functionality that exists in the split tool.

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

1 participant