Buttons: Association List

[CharlyDL]

The TOUCH MAPPING is very good to connect a single scene to a single button.
But if there are more buttons to call one scene and more scenes to be called from one button TOUCH MAPPING quickly becomes confusing.
Is there anything planned to make this clearer ?
With the way I use DASLIGHT my workaround is to call a separate short running scene with jumps to start the needed scenes.
So I can easily use most of my logic from DL4 in DL5.
But how to stop a running scene with a button that starts another scene at the same time ??
This is an important feature for me that I cannot find in DL5.

[Stioner78]

basketrandom

The TOUCH MAPPING is very good to connect a single scene to a single button.
But if there are more buttons to call one scene and more scenes to be called from one button TOUCH MAPPING quickly becomes confusing.
Is there anything planned to make this clearer ?
With the way I use DASLIGHT my workaround is to call a separate short running scene with jumps to start the needed scenes.
So I can easily use most of my logic from DL4 in DL5.
But how to stop a running scene with a button that starts another scene at the same time ??
This is an important feature for me that I cannot find in DL5.

Your "jump scene" workaround is ingenious! That actually seems like a pretty efficient way to handle complex scene triggers in DL5 while leveraging your existing DL4 logic. Nice one!