Is it possible to use a colour variable with functions

[Danake]

I’m trying to cut down on available space and one way would be if I could use a function from Fett’s config helper for the crystal chamber. My crystal is its own blade and the only thing different across styles is the colour.

For example: (code made up to try and explain what i’m looking for)

using crystal = Layers<
  Pulsing<Mix<Int<8192>,RgbArg<BASE_COLOR_ARG,Black>,RgbArg<BASE_COLOR_ARG,FunctionArg>>,RgbArg<BASE_COLOR_ARG,FunctionArg>,8000>,
  InOutTrL<TrInstant,TrInstant,Pulsing<Mix<Int<8192>,Black,RgbArg<OFF_COLOR_ARG,FunctionArg>>,RgbArg<OFF_COLOR_ARG,FunctionArg>,2000>>>>()



StylePtr<crystal<FunctionArg<red>>>()


etc..

[Fett263]

Yes, in OS7 you can set any of the style arguments for a style or using in your config. But you need to use Rgb16 values for each color you want to edit in the correct order and “~” for a value that is missing or should use the default.

The correct syntax would be (based on your using function):

StylePtr<crystal>("65535,0,0 ~ ~ ~ "),

See discussion here:

ProffieOS6 & 7 Config Helper Tool v.2

Here’s an example that seems to work. StylePtr<CrystalHyperResponsiveRotoscopeOriginalTrilogyDodgerBlue>( "65535,0,0 ~ ~ ~ ~ ~ 0,65535,0 ~ 0,65535,0 0,65535,0" ), I was hoping to be able to do something like the following to make it more human readable, but from what I can tell, that’s not possible. Will definitely work for making a complex style and reusing it multiple times. StylePtr<CrystalHyperResponsiveRotoscopeOriginalTrilogyDodgerBlue>( "65535,0,0 " // BASE_COLOR_ARG = 1, // Primary Base Color "~ " //ALT_COLOR_ARG = 2, // Alternate or Force Color (free-use) "~ " //STYLE_OPTION_ARG = 3, // Style Option "~ " //IGNITION_OPTION_ARG = 4, // Ignition Options "~ " //IGNITION_TIME_ARG = 5, // used in IgnitionTime alias "~ " //IGNITION_DELAY_ARG = 6, // Ignition Delay Time "0,65535,0" //IGNITION_COLOR_ARG = 7, // Ignition "Power Up" Color "~ " //IGNITION_POWER_UP_ARG = 8, // Ignition "Power Up" Options "0,65535,0" //BLAST_COLOR_ARG = 9, // Blast Color ),

Style argument info here:

Style Arguments

This will be coming to the Config Helper tool as well, more explanation and demo here:

ProffieOS7 Config Tool, Using Functions and Style Arguments Sneak Peek

[Danake]

Awesome, appreciate the help. Got it working

[Danake]

I did notice in your os7 builder when generating the config it removes the quotes from ("65535,0,0 ~ ~ ~ "),

[Fett263]

I am still debugging the config tool that was just a demo video of what’s to come

[Danake]

Ah I hate to bring this up again, I thought it was working but its not with functions. For the actual function does it matter what color is set to begin with. For example if I have the function as blue default but I want a preset red I have:

using crystal = 
Layers<
  RandomPerLEDFlicker<RgbArg<BASE_COLOR_ARG,DeepSkyBlue>,RgbArg<ALT_COLOR_ARG,Blue>>,
InOutTrL<TrInstant,TrInstant,Pulsing<Mix<Int<8192>,Black,RgbArg<OFF_COLOR_ARG,Blue>>,RgbArg<OFF_COLOR_ARG,Blue>,2000>>>;

And preset to change to red:

StylePtr<crystal>("65535,0,0 ~ ~ ~ "),

When I change to the preset it remains blue

[Fett263]

It works the same for using function, it doesn’tmatter what default is set. Would need your full config.

Edit:
Do you mean the OFF_COLOR_ARG?
That is the 31st argument so you need to set it accordingly as the 31st argument in the string.

profezzorn/ProffieOS/blob/c39daac1642affd724891e05e2c596571236d3ac/styles/edit_mode.h#L41

("65535,0,0 ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 65535,0,0")

[Danake]

yeah you are right, works now