Sign In:     

Forum: General Discussion
Topic: Script School - Page: 53
A few things added in BUILD 8663 that I think need some notes.

-settings script can update more settings
-setting script accepts script as second parameter
-browsed_song_hashtag and loaded_song_hashtag scripts to add/remove hash tags from user 1, user 2 and comment field
-effect_arm_* scripts support fx units as first parameter (1 or 2, with 3 slots per unit)

-settings script can update more settings
well that's a bit vague, but I did some testing here's what I've found

setting browserShortcuts
setting browserShortcutsIcons
setting colorRules
setting quickFilters
setting rootfolderslocation
setting skinsplitstate
setting browserColumns

are now all scriptable, example case
setting colorRules 'red=Exists = 1,...'

This change means most* of settings are now scriptable.

I'll show you something I've used this for that I think is pretty handy [in a browser administration kind of way]
First I get my browser exactly how I like it, the dividing lines between folders/songs/sideview where I like them [the proper name is "split(s)"]
I then also get my browser columns exactly how I like them; in order and spaced the column splits how I like them
I made a custom_button called SAVE, I gave it this script
get_text `setting browserColumns` & param_cast & set_var '@$browserColumns' & get_text `setting skinsplitstate` & param_cast & set_var '@$browserSplits'

I press the button to save these settings.
I then made a second custom button called "RESET" with this script
get_var '@$browserColumns' & param_cast & setting browserColumns & get_var '@$browserSplits' & param_cast & setting skinsplitstate


I can now totally change my browser, move the splits, remove columns, add columns, make a real mess [like all guests on my rig seem to need to do]. And then all I have to do it press my RESET button and my browser is restored to how I like it. Ah zen :)

the layout is just saved and recalled from a variable so you could have as many save states as you need with a different variable name [just always start with @$ to make it a persistent global variable]

This leads me to the second thing
-setting script accepts script as second parameter
remember our RESET button earlier? We can do this now instead of the param_cast :)

setting browserColumns `get_var '@$browserColumns'` & setting skinsplitstate `get_var '@$browserSplits'`


Video demo



The third thing
-browsed_song_hashtag and loaded_song_hashtag scripts to add/remove hash tags from user 1, user 2 and comment field

example
browsed_song_hashtag 'user 1' '#bouncy'

param 1 is the tag, param 2 is the hashtag string to add/remove.


More; There's almost certainly things you could do with
setting browserShortcuts
setting colorRules
setting quickFilters
that could be useful in some cases, I haven't fully studied.

Lastly
-effect_arm_* scripts support fx units as first parameter (1 or 2, with 3 slots per unit)
I haven't studied this at all yet, so I'll make another post when I have.
 
Since set_var also accepts a script parameter, you could further tidy up the storing of settings as well
set_var '@$browserColumns' `setting browserColumns`
 
oh of course yeah, I think of set_var as only strings, but without " or ' a `script action` will parse as a string.
 
Thank you so much to add the tagging verb (browsed_song_hashtag ) and to follow my suggestion.
This makes tagging using a pad so much easier.

You guys simply rock!