Closed Jeff0S closed 7 years ago
From fingersmcgarnickle on April 18, 2010 06:00:12
I prefer no menu and let the user customize Reaper the way they want. I might be the only one, though. Maybe post in the forum to see if anyone would object to a restructure? and to get ideas from people using it.
I feel that things which load another window like the LFO gen etc should be in the extensions menu in the main menu bar. Things that do simple actions should be in the context menus.
From jeffos...@gmail.com on April 19, 2010 07:52:53
Totally aggree with the OP: too much things in there and even I think that since day one as an end-user (even a bit messy, I'd say!).
I'd go even further but this is only -my- opinion: I don't like "Extensions: Take/item manipulation" & "Extensions: Take/item selection" item sub-popups, same goes for the way too long "Misc/Experimental" sub-popup (main menu) : those actions should just be present in the action list (its filter is perfect for that). In fact, there should be no intrusion in native popups AT ALL (this is what I do, at least): like fingers said, we can now let the user customize those menus + floating toolbars! But I guess this is too radical/touchy now: e.g. removing things like "SWS snapshots" from the track popup-menu could make some noise!! But this is one indeed belongs to "the best and most usable features"..
From mario.kr...@gmail.com on May 12, 2010 11:33:45
Perhaps arrange the commands in the menus according to the now released SWS manual?
From mario.kr...@gmail.com on May 28, 2010 02:12:43
Or contact Mike Stop Continues? http://forum.cockos.com/showthread.php?t=58672
From mario.kr...@gmail.com on May 29, 2010 05:13:46
Also, suggestions to rename actions for consolidation with native action wordings.
That would be it!
From jeffos...@gmail.com on May 29, 2010 05:56:47
thanks a bunch for this accurate report Mario!
For my part, I agree on all points (+ more consistent with native actions). I'll take care of S&M and Xen actions, I prefer let Tim & Padre check if they're ok for their actions..
About the OP (default SWS extension menus), I'd increase a bit the priority: I know this leads to a cumbersome opinion/vision of the exentions to some users. I said what I'd do for context/popup menus (just my opinion, may be a bit too radical) but what proposes Fingers for the main menu's "Extensions" seems a good and reasonnable start..
From jeffos...@gmail.com on June 07, 2010 11:24:24
Xen and S&M actions renamed as proposed in r149 , v1.7.2 #9
Status: Started
From mario.kr...@gmail.com on June 07, 2010 11:43:10
Great! Let's wait for Tim and Padre, then :)
From mikestopcontinues on June 11, 2010 11:51:12
Hey, I would actually be very happy to build a new Extensions menu if you want it. The one present in ReaMenus currently only shows those action sets that weren't already incorporated into the other menus, but I'd be happy to build an Extensions menu with all the SWS actions in the same place... or rather, all that will fit. There's actually more SWS actions than the menu system can support. Found that out the hard way. ;)
Let me know. http://forum.cockos.com/showthread.php?t=58672
From mario.kr...@gmail.com on June 11, 2010 11:58:58
There you go, the man himself! :D
From jeffos...@gmail.com on June 11, 2010 15:07:05
Hi Mike, yeah, this would be welcome, sure! Thanks the proposition!
From mikestopcontinues on June 16, 2010 05:48:04
Hey, I just wanted to let you know I'll have it ready by Saturday. This week's been a bit busy.
From jeffos...@gmail.com on June 17, 2010 04:56:31
Thanks Mike!! Hey, take your time.. no hurry! About the ReaMenu thread: I saw it of course, I see that SWS Extensions are mentionned a lot there, I've seen questions too.. So, just to let you know: I didn't chime-in there 'cause I'd just prefer Tim to do it. Thanks again. Jeff
From mikestopcontinues on June 17, 2010 10:59:58
Hey, I've progressed much of the way through the menu. I've still got a lot to sort through, but I thought while I did, you might be able to answer a few questions about the following actions:
"select last track of folder" yields "NOT IMPLEMENTED!" I searched for an issue, but there wasn't one. I thought perhaps this is going to be implemented so soon that it doesn't need one, but I'll be happy to file one if this wasn't intended.
"Make folder from selected tracks" is poop compared to "Set selected tracks as folders". The latter works in more situations and auto-colors properly. I would file another report to have them merged because there isn't one yet, but I wanted to make sure I wasn't missing something vital that would require them both.
"Store current selected takes" and "Recall selected takes" seem like they would be useful in custom action making, but their names are all wrong. It should be more like "Save current active takes in selected items" and "Restore active takes across tracks" or some such.
Finally, I've found no bug report for "Nudge section loop..." They don't work for me, but since there's no bug report, I want to know if they work for others, so that I can include them on the menu.
Anyway, I didn't want to file a bunch of bug reports before checking about them first.
Thanks!
From swstim on June 17, 2010 20:20:41
Thanks Mike, I haven't been coding too much because the weather's too damn nice but will take a look at these items soon.
Tim
From mikestopcontinues on June 18, 2010 17:48:25
Thanks! You guys really bring a lot to REAPER.
To that list, I'd like to add these, which also don't seem to have issues in the tracker: "Switch grid spacing" -- doesn't do anything and there doesn't seem to be a parameter connected to it anyway
"Remap item positions..." doesn't work.
"Toggle auto-fade to default" and "Toggle default fade time to 0" (I might have the names of these two wrong) are buggy.
I should add that the menu is complete with just under 1000 items. I'm going to proof it once more before I post it here tomorrow.
From mikestopcontinues on June 19, 2010 11:09:25
Here it is. I hope this exceeds your criteria. Let me know what has to be improved.
Attachment: Extensions.ReaperMenu
From mario.kr...@gmail.com on June 20, 2010 03:14:39
There are a lot of actions duplicated which are implemented in other places on ReaMenus, right, Mike? Dunno if I see that as useful or not - since a lot of SWS functionality is put on other places, I thought you'd focus on actions which aren't used elsewhere in the menus. But I guess this is more like a reference view of SWS actions. However, IMHO it might be better to just sort the actions which aren't used elsewhere in ReaMenus (or make two versions of Extensions menu - one for ReaMenus without duplicated entries from other menus, and one for regular users which don't use ReaMenus and need to have everything in one place).
Also, swipe the menu with search&replace for these ;)
db -> dB bwav -> BWAV some slots have leading zero (01, 02), remove the leading zero ;) ruler red -> red ruler ids -> IDs play rate -> playrate fx -> FX csound -> Csound (un)mute, (un)select and similar -> toggle mute, toggle select ;)
What happened to ReaScript submenu, it couldn't fit?
From mikestopcontinues on June 20, 2010 07:47:55
Mario, I was under the impression the idea was to make a comprehensive menu set for SWS. I should point out that ReaMenus already has a revised Extension menu which DOES only show those SWS actions not available elsewhere.
Also, thanks for the edits! I'll implement them ASAP. (Except that project templates and track templates have leading zeros because that's how you must name the templates for those features to work.) I was trying to move away from 'toggle's but I guess it's the cleanest way to put it.
From mario.kr...@gmail.com on June 20, 2010 07:52:09
Oh, that clears it out, then! Are you talking about impeding ReaMenus #008, with the new Extension menu? :)
Yeah, no go without toggles :P
Thanks for your hard work, and sorry if I missed the point of this menuset here!
From mikestopcontinues on June 20, 2010 08:09:41
Heck, you're the one sent up the bat signal! lol. It was actually my first visit to the google group and I thought, "Everywhere you go: there you are."
Of course, I've /thought/ about adding the new extensions menu to ReaMenus because it would be sad to have ReaMenus overwrite it, but I could always just add the option to the splicer to use the 'full' Extensions menu. Just wait til you see the coolness of the "Options" options for ReaMenus 008.
I should also say that if there were a way to add ReaMenus to SWS, perhaps to enable/disable ReaMenus as the 'default' menu set, I would agree in a heartbeat. The best thing for REAPER users is to have to do as little as possible to get the program up to snuff. That one groovy extension that hasn't joined SWS yet just rubs me wrong, you know? Especially when you look at the "automation" submenu on the Extensions menu.
From mikestopcontinues on July 06, 2010 17:58:58
I was just wondering if Jeff/Tim/whoever else has had a chance to check out the menu and let me know how/what I should improve. Let me know!
From jeffos...@gmail.com on July 07, 2010 03:06:54
oops!! Sorry Mike, I tried it of course, forgot to say that IMHO, way, Way , WAY much better than the current ext. menu! Let's here from Tim, now..
From dagancpl...@gmail.com on October 12, 2010 13:24:48
Great work mike! Much easier to trace/reveal the features of the extension
super like...
Out of date.
From swstim on April 18, 2010 05:20:28
There's a lot of new SWS features, and the old "Extensions" menu is getting long in the tooth. I think the menu should be totally restructured to reflect the best and most usable features.
If anyone has any ideas about menuing, please comment!
Original issue: http://code.google.com/p/sws-extension/issues/detail?id=119