Skip to content

Correct the 'continue' button functionality#70

Open
pbelbin wants to merge 4 commits into
TuomoKu:masterfrom
pbelbin:master
Open

Correct the 'continue' button functionality#70
pbelbin wants to merge 4 commits into
TuomoKu:masterfrom
pbelbin:master

Conversation

@pbelbin
Copy link
Copy Markdown

@pbelbin pbelbin commented Nov 2, 2022

It appears that the 'steps' value is not being defined within the template definition, and so it's not available for inclusion in the playout/rundown item, where it doesn't treat the 'continue' button properly.

This one line change fixes that issue.

Users will need to re-import the template and re-build the playout/rundown items, but at least, from that point on, the 'continue' button will work like it should, from what my testing shows.

Without having the 'steps' value available in the template, there's nothing to copy when building the rundown, hence the 'continue' button does not function properly.
…lity-for-multi-steps

Provide 'steps' value to template definition
@pbelbin
Copy link
Copy Markdown
Author

pbelbin commented Nov 2, 2022

Hmmmm. Seems there's more to it - 'saving' the template (eg: after configuring the server value) seems to be discarding the 'steps' value?

Particularly when editing the template.  Previously, would discard the steps value
@pbelbin
Copy link
Copy Markdown
Author

pbelbin commented Nov 3, 2022

@TuomoKu , please take a look. Seems that this makes the 'steps' value be saved now, across edits of the project templates (eg: setting the casparCG player target) and this allows the 'continue' button to behave like it should during playout too.

I may have gone a bit further than strictly needed, but at least it's working for me locally.

Have not tried saving and importing via CSV file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant