Anything can be a WALTER variable now

[sockmonkey72]

Originally Posted by White Tie

Anything can be a WALTER variable now because that's how theme scripting works. See HERE.

I meant the other way around, like this.

[White Tie]

You can do that with theme scripting.

[sockmonkey72]

Originally Posted by White Tie

You can do that with theme scripting.

I don't think you can, but I'm happy to be proven wrong. Please explain how I get access to the record-monitor (on/off) or record mode state for a track from WALTER. At the moment, only 'recarm' (0/1) is available.

So let's say that I would like the track name to be displayed in RED if the track is armed, but BLUE if the track is armed for monitor-only usage (that is, "Record: disable (input monitoring only)" is set), and WHITE if the track is unarmed. That is what I am trying to achieve.

Thanks!

[White Tie]

string retval, integer flags = reaper.GetTrackState(MediaTrack track)

Gets track state, returns track name.
flags will be set to:
&1=folder
&2=selected
&4=has fx enabled
&8=muted
&16=soloed
&32=SIP'd (with &16)
&64=rec armed
&128=rec monitoring on
&256=rec monitoring auto
&512=hide from TCP
&1024=hide from MCP

to do a layout change.

[White Tie]

Moving this because it was OT.

[sockmonkey72]

Originally Posted by White Tie

string retval, integer flags = reaper.GetTrackState(MediaTrack track)

Gets track state, returns track name.
flags will be set to:
&1=folder
&2=selected
&4=has fx enabled
&8=muted
&16=soloed
&32=SIP'd (with &16)
&64=rec armed
&128=rec monitoring on
&256=rec monitoring auto
&512=hide from TCP
&1024=hide from MCP

to do a layout change.

You are suggesting that I trigger a new theme layout for a track by virtue of a memory-resident script which polls all tracks continuously for changes to the record-monitor state?

That's not what I asked, and it's also, I hope you would admit, kind of overkill for changing the text color in response to a track property. In the same way that the scalar value "recarm" is available for use wrt the record-arm on/off state.

Anyway, thanks for putting some thought into it. I am not 100% that we're understanding each other, although I've tried to explain my use case clearly. I can't imagine you using a grotesque mechanism like the above in your own themes, though, so I have trouble imagining that you'd suggest it to me as a reasonable solution for/dismissal of the simple matter/request for some more scalar values.

[White Tie]

Do you want to do your thing or not? FWIW You only need to poll when this changes:

integer reaper.GetProjectStateChangeCount(ReaProject proj)

returns an integer that changes when the project state changes

[sockmonkey72]

Originally Posted by White Tie

Do you want to do your thing or not?

Yeah, not like that. First and foremost, it's not easily transferrable to someone else's machine without complex instructions, so it's not appropriate for a visual indicator in a distributed theme.

Again, thanks for considering my observation/request.