-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Menu entry "remove all linked controllers" is bad wording #5285
Comments
For what it's worth, Serum calls its equivalent "Remove all modulators". Alt proposals:
I think your second proposal is too long and "model" is a concept that the user shouldn't have to care about. After that I don't have much of a strong preference. Link/linked saves a few characters over connection/connected and is maybe less ambiguous, although the second point is minor and probably varies from person to person. |
If we remove connections... |
Sounds good, though it still sounds like removing the modulators
Like mentioned above, connections don't always go to controllers. So I'd be for "Disconnect everything". If no one disagrees within a few days, I'll open a PR. Can such a PR go to stable-1.2? I ask because this will invalidate any translations... Not so good for a stable release? On the other hand, it's a bug fix... |
I disagree because users may think it disconnects automation patterns. |
Oh, so it disconnects everything except automation tracks? That's hard to convey concisely. What about something like "unlink controllers/knobs" then? Length comparison of a few variants. I'm partial to the first: "unlink controllers/knobs" |
I just tested what PhysSong said, it's indeed correct.
It's not just knobs. Can be LEDs, LCD widgets, whatever. That's why I proposed models, but I agree that no one understands that. Maybe "widgets"?
That's the current wording, with the issues mentioned in the 1st post. Another idea: "Disconnect all except automation". |
Yes, I put it there as a reference for the current length of the string. Anyway, what if we let "driver" = a knob* that drives another knob's value. Then we have a name to refer to these linked models (specifically to the master model) and can write "Disconnect controllers and drivers". I think that's a bit more UI friendly than "Disconnect controllers and models". *knob/LED/whatever. |
Hit the wrong button, again. I've edited my comment above to what it ahould have been. |
I'm against introducing new vocabulary like "driver", but I like the idea of your removed post to name them "controls". "Disconnect all controllers and controls" sounds good to me. Or "Disconnect all modulators" like in Serum. |
Well, it's not exactly "new" vocabulary, although I guess it depends on
which scope you're considering.
https://docs.blender.org/manual/en/latest/animation/drivers/index.html
The concept is pretty similar, for example:
"Control a property with an object’s transform. In this example, the Y
rotation of Object 2 will be driven by the X position of Object 1."
This seems quite similar to connecting models imo, and the term "driver"
would be future proof in case the functionality were expanded upon.
|
I was so wrong. This comes from a German translation:
You don't need to be a German expert to understand what they translated wrong. I still don't like "Remove", but don't see it as critical. I'm fine with a transifex fix for the German translation. |
Solved in transifex. |
It's bad because:
Proposals:
What shall we use?
The text was updated successfully, but these errors were encountered: