Missing Arguments?

alexs1

I noticed after combing through the functions in build 40 that I couldn't find any way to edit function arguments from the bindings window. Searching the forum, I came across this topic, which shows an example of a missing argument box from the edit panel and seems to be the case for most functions in the tree for me.

jeff

Which functions were you trying to give arguments?

Almost none of the built-in functions use arguments, every script should though.

LoadMidi was one of the ones I missed, if that's what you need, you can patch it as described in that linked topic.

I'll be finishing up the next build in a day or two if you want to wait, but it isn't hard to patch if you're careful.

Ahh, I see from a post reaction that you're probably interested in SpeedShift arguments. I see that there isn't actually a function named SpeedShift, thought there was, let me figure out what that's called.

alexs1

jeff

Hey!

I wanted to see if I could add an argument to a binding for SpeedStep and some of the other speed functions to try out varispeed with different semitone intervals. I also wanted to assign a value argument for TrackSelect for simple non-script triggers. I remember there being an argument field built in to the edit panel before that would work with relevant functions. It can be more convenient to add an argument than write a script, which is what I was looking for. Not sure if it was a bug—feel free to change the tag if not.

jeff

Most of the Speed functions need arguments in the UI so that's a bug.

TrackSelect has an argument, but what happens now is that if a function has an argument that can be presented in a nicer way than a text box, it tries to do that. For TrackSelect there will be a field in the binding named Track To Select which will have a menu of track numbers. That's actually just filling in the binding arguments with a number but it has a more obvious name next to it and it only allows valid track numbers.

alexs1

jeff

Gotcha. I remember reading in another post that you were working on replacing the generic argument field with neater menus like Track Select. For speed-related functions, I'm guessing you would have a field like "Semitones" instead of an argument where you can type in a number. Were arguments always taken as a single value? Or were there some functions that take strings, too?

jeff

Binding arguments are a string that is passed along to the function handler, which then deconstructs it. Most of the time, it just converts it into a single number. A few like TrackGroup recognize special keywords like "clear" and "next".

The argument string isn't making it's way into scripts yet, but eventually it will so you can run a script from a binding and pass multiple words and numbers into it separated by spaces or commas

alexs1

jeff

Makes sense. Do you think arguments for Speed bindings could make their way into the next build?

jeff

Yes, finishing it now. Also fixing script bindings failing to show any Send To or Arguments fields