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

[BUG] Some buttons don't draw #2832

Open
2 tasks done
AHub88 opened this issue Apr 10, 2024 · 4 comments
Open
2 tasks done

[BUG] Some buttons don't draw #2832

AHub88 opened this issue Apr 10, 2024 · 4 comments
Labels
BUG Something isn't working
Milestone

Comments

@AHub88
Copy link

AHub88 commented Apr 10, 2024

Is this a bug in companion itself or a module?

  • I believe this to be a bug in companion

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

Hi,

I have updated from 3.1.2 to 3.2.2.

Everything is normal up to page 8.
From page Nr. 8 onwards, ALL buttons have disappeared.

BUT only the labels are missing.
The Press Actions are still there.

Clipboard_04-10-2024_03

Can you please help me?

Andi

Steps To Reproduce

No response

Expected Behavior

No response

Environment (please complete the following information)

- Companion Version: 3.2.2 and 3.3.0

Additional context

No response

@AHub88 AHub88 added the BUG Something isn't working label Apr 10, 2024
@AHub88
Copy link
Author

AHub88 commented Apr 10, 2024

A downgrade solved the problem (temporarly).
But I would still like to solve the problem.

@Julusian Julusian changed the title [BUG] A few buttons are gone after update [BUG] Some buttons don't draw Apr 10, 2024
@Julusian Julusian added this to the v3.3 milestone Apr 10, 2024
@Julusian
Copy link
Member

I remember someone else having this issue, which was concluded to be the graphics rendering 'crashing' when encountering certain unicode characters in the text.

I have a feeling a fix wasn't found for this yet, they solved it by removing the problematic unicode characters and restarting companion. The proper fix could be #2785, which needs more testing

@AHub88
Copy link
Author

AHub88 commented Apr 12, 2024

THX, yes it was a unicode character.
After a restart the problem was solved.

@Julusian Julusian modified the milestones: v3.3, v3.4 May 16, 2024
@Julusian
Copy link
Member

This is fixed in the 3.4 beta builds

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG Something isn't working
Projects
Status: Done
Development

No branches or pull requests

2 participants