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 ability to accept or reject changes individually #568

Open
Thallassa opened this issue Apr 20, 2016 · 5 comments
Open

Add ability to accept or reject changes individually #568

Thallassa opened this issue Apr 20, 2016 · 5 comments

Comments

@Thallassa
Copy link

This is something mator and I had discussed as desirable, and I mentioned it to Freso and he said I should put it here as a feature request.

Basically, when LOOT decides to move mods around, you can either click "apply" (thereby accepting all its changes), or close it (thereby accepting none of its changes).

It would be nice to be able to accept some changes, but override others (without necessarily making a meta rule every time, especially as I've had issues with circular meta data in the past...)

@Freso
Copy link
Member

Freso commented Apr 20, 2016

I really like this idea. I'm imagining it kind of similar to how a git add --patch (or git commit --patch) works, but @WrinklyNinja knows better how it could actually work in LOOT. Combined with #377 and/or #555 it would make LOOT much more flexible.

It should possibly be a toggle though.

@Ortham
Copy link
Member

Ortham commented Apr 20, 2016

It's a neat idea, and upon first thought is technically feasible, but do you have any suggestions for what the UX would be like?

@Thallassa
Copy link
Author

... This was a month ago? Oh man, I'm sorry.

It kind of depends on how #377 might look, but one thought I had was highlighting the plugins that changed position, possibly indicating how many positions they changed and in which direction (like red up arrows and green down arrows with a number next to them), and then a check mark to accept the change and a red box to decline.

Could be simplified with just an "accept" box next to each changed plugin.

My understanding is that the next version will only move plugins that need to move (current version moves plugins that don't need to move, alphabetically), so that would simplify it as only... oh, I dunno... like 60% of plugins would need to have changes individually applied during use.

@Ortham
Copy link
Member

Ortham commented May 19, 2016

My understanding is that the next version will only move plugins that need to move

That change happened in v0.7.

@Thallassa
Copy link
Author

Thallassa commented May 19, 2016

It did? I'm using.... 8.1... I'm bad at versions and my plugins are still sorting alphabetically, when there are no particular rules. Certainly every single plugin I've looked at, moved.

@sibir-ine sibir-ine added the ui label Feb 3, 2022
@sibir-ine sibir-ine changed the title Ability to accept changes or ignore them individually Add ability to accept or reject changes individually Feb 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants