Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Possible Improvements to Cycle Editor #565
From OuttrOMu...@gmail.com on April 24, 2013 01:40:44
Hi again, I've been using the cycle action editor a lot lately and I wanted to suggest a couple changes that would really speed up creating cycle actions for users (me).
Ideally, like this:
Selected Action (in the actions window)
(I don't know how to use the command action, so that's the only reason I put it at the bottom, but this way the eye can just scan down for one key, capitalized word, instead of reading "Add/Insert 5 times and potentially getting confused (as in my case :))
Original issue: http://code.google.com/p/sws-extension/issues/detail?id=565
From jeffos...@gmail.com on April 26, 2013 07:04:16
Thanks for entering a ticket
From OuttrOMu...@gmail.com on April 27, 2013 13:14:36
well that was fast! as to #4, the least confusing wording for me would be "Manually Type Command ID," or "Add via Command ID." "free command," imo is not literal enough. and perhaps just choosing "add" or "insert" instead of "add/insert" would suffice. for me, more important is the write Menu Entries as Titles (with capitalization. It's much easier to find a key word scanning the entries for capital letters. It's one of the main reasons I spent so much time redoing the Reaper menus from scratch, and just a suggestion.
one unrelated question: is python worth learning as an intro programming language and probably the only one i will bother to learn? I'd like to do stuff like this for reaper myself, but unless i can do a lot of other things with the knowledge, i probably won't spend the time.
From OuttrOMu...@gmail.com on April 05, 2014 17:14:56
Hi again. Not sure if any devs will see this since it's a closed issue, but these changes got unimplemented in recent versions, so I wanted to restate my case:
Maybe not for you devs, but certainly for most end users, "Add Selected Action (in Actions Window) will be most often used. It should be at the top of the list. "Add" should be second, for those in the know.
And as far as "plain english" goes, "Add/Insert" is vague and unclear. "Add/Insert Command ID" would be much more descriptive. Also "Statement" is also too general and unclear to the layman. "Condition" would be much more specific and to the point, since not all statements are conditional.
One last thing: I originally got you guys to agree to add END statements for the conditions, perhaps you could take it a step further and automatically delete any extra END statements when adding a condition? E.g. I add an IF by accident, delete it and add a NOT IF instead. Now i have an extra END statement unless I notice it or I apply changes and get a warning. Would be cool if adding a new condition would fix that automatically. Nitpicking...
Btw, the indented conditions do make the cycle actions much easier to read, thanks for that.
If I don't get any response to this, I'll open a new issue.