-
Notifications
You must be signed in to change notification settings - Fork 1
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
Rename "Toggle Glug/Unglue" scripts to "Smart Glue-Unglue" #59
Comments
Hold fire One other thing I thought is, the rest of the actions are all called Glue (Reversible) One of the things I was thinking was maybe something like GR (Quick - Toggle between Glued and Unglued, Only works with one stage of glue) or something I dunno I think they should all be labelled and prefixed exactly the same and then demarcated after the delimiter |
As a long-time Reaper user, I can attest to a personal bugbear of mine, I hate when Scripts are disorderly in the actions window. I like when things are clear, and if there's a function or family that belong together for whatever reason, then that should be very clear in the actions window |
I'm also starting to feel that "Glue (Reversible)" is becoming lightly problematic as a name and wonder whether it should be Glue-Reversible instead |
good points. something like this? MB_Glue (Reversible): Glue container item... |
Yeah see, something like that is much more preferable to me, and flows with a harmony of conscience and design |
The parentheses really don't scan well do they |
Edit #64 |
Yeah, there's a few other points though
Having said that in an ideal world, I wish Reversible wasn't such a long word, as I like to get to the parentheses content sooner rather than later, visually. In other words I'm still flexible with the name, doesn't have to neccessarily be that. Can be Glue-Rev or whatever, GlueFlex, Glue-History |
Re parentheses, exactly. I like Reversible a lot though. It's the clearest UX |
yea alright that's cool, Reversible works just fine |
1.30 |
No description provided.
The text was updated successfully, but these errors were encountered: