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

Samsung QN55Q6FNA double registration of directional inputs #36

Closed
Window-Hero opened this issue Jun 15, 2020 · 10 comments
Closed

Samsung QN55Q6FNA double registration of directional inputs #36

Window-Hero opened this issue Jun 15, 2020 · 10 comments

Comments

@Window-Hero
Copy link

I have installed the client on a Samsung QN55Q6FNA, and whenever you input a direction on the remote that input is registered twice, causing you to select the menu item two entries over. This makes menu navigation extremely tedious when there are an even number of entries, and impossible when there are an odd number.

@dmitrylyzo
Copy link
Collaborator

dmitrylyzo commented Jun 15, 2020

This should have been fixed once and for all by #30.
What jellyfin-web and jellyfin-tizen commits do you use?

@Window-Hero
Copy link
Author

I don't have a record of that, but my files are all date stamped June 4, so I downloaded them shortly before that fix got merged. I will recompile and report back.

@Window-Hero
Copy link
Author

Gah, trying to recompile I'm getting a "'console' is undefined" error. I remember I had this issue last time but I can't remember what I did about it.

@dmitrylyzo
Copy link
Collaborator

Windows?

@Window-Hero
Copy link
Author

Yeah, I ran yarn on Linux and then pushed the files over to Windows for the final compile with Tizen Studio.

@dmitrylyzo
Copy link
Collaborator

If you do this from command line, then you should use tizen.bat instead of just tizen.

@Window-Hero
Copy link
Author

Thanks, that was going to take me awhile to work back around to.

@Window-Hero
Copy link
Author

This fixed it, thank you. This is the first time a bug has ever been fixed in the time between me finding it, and me posting about it.

@dmitrylyzo
Copy link
Collaborator

Actually, first appearance of this issue was #4

@Window-Hero
Copy link
Author

Yeah, I saw you reference it, I didn't catch that in my initial check of the issue tracker because the title wasn't clear, and it was far enough back that I didn't read the whole string.

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

No branches or pull requests

2 participants