Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segment display replace #1840

Open
wants to merge 3 commits into
base: dev
Choose a base branch
from

Conversation

mpcarr
Copy link
Contributor

@mpcarr mpcarr commented Sep 22, 2024

This PR addresses issue #1839. The newly added replace feature ([https://github.com//pull/1779](Segment Displays: Stack vs Replace Option).

This update using the current states color, flashing and flash_mask settings for the incoming text if non are specified on the segment_display_player. Without this, the text isn't displayed due the the color being missing and the text is set to flash.

Additionally this update removes the text from the display when the update method is not stack.

When using replace update method the default flashing, mask and color props are empty or none. This causes the text not to displayed or flashed when it shouldn't be. This update uses the current state's settings for new text if none are set.
Copy link

@avanwinkle
Copy link
Collaborator

Thanks for the input, have you looked at #1820 to see where your respective changes align/diverge?

@worldpeace-germany
Copy link
Contributor

@mpcarr the PR @avanwinkle has referenced is from me. I believe my fix should cover your case and even some more. I have the impression that segment displays are not that widely used and it is hard to get test cases validated. Would you mind to test my code changes in your project and report back? If you find issues I am willing (happily with you together) to fix these to get a better segment display support into mpf.

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.

3 participants