Add applicable ClipSlot methods to Scene (isPlaying, etc...) based on combined nested ClipSlot states.

[joslarson]

trafficstars

When representing a ClipSlot using the Control Surface API I am able to render the midi control differently based on the results of the hasContent, isPlaybackQueued, isPlaying, isStopQueued, isRecordingQueued, and isRecording methods. For instance I might have the LED associated with a PAD or Button on my controller be off if there is no content in the slot, dim if it has content, on (full brightness) if it is playing, and flashing if it is playback or recording queued.

It would be nice to provide the same interactive feedback for scenes. The idea being to add the hasContent, isPlaybackQueued, isPlaying, isStopQueued, isRecordingQueued, and isRecording methods to the Scene where they fire and evaluate to true when all of the scene's existing nested clips share that same state as follows:

method	description
hasContent	Evaluates to true when the scene contains at least one clip.
isPlaybackQueued	Evaluates to true when all of the scene's existing clips are playback queued.
isPlaying	Evaluates to true when all of the scene's existing clips are playing.
isStopQueued	Evaluates to true when all of the scene's existing clips are stop queued.
isRecordingQueued	Evaluates to true when all of the scene's existing clips are recording queued.
isRecording	Evaluates to true when all of the scene's existing clips are recording.

[git-moss]

You can work around this for the time being by creating a trackbank with a very large number of slots per page (e.g. 1000) and monitor the states yourself.