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

Keyboard Layout for Razer Blade stealth, doesn't allow you to select all the keys. #11

Closed
hhollenstain opened this issue May 30, 2016 · 17 comments
Labels
device map Adds or modifies a device graphic device specific Only affects specific hardware feedback Opinion and thoughts to be taken on-board
Milestone

Comments

@hhollenstain
Copy link

I was able to map most of the keys using the layout on my RBS but the F1 Key, the left arrow, enter, and z keys can't be mapped from the UI. Not surprised because this tool is designed for the full sized keyboard layout. This would be possibly a great new feature to be able to select the layout when making a custom key mapping layout.

@lah7 lah7 added the feedback Opinion and thoughts to be taken on-board label Jun 2, 2016
@terricain
Copy link
Contributor

Might be something to do with the mapping dictionary. I'll have a look Friday.

@RetroEggy
Copy link

Similar issue with the Blackwido X Chroma, Space and the FN Button can't be selected from the UI. Using a preset like static etc. works fine, however (btw congrats on the ppa, I'm so happy that pretty much everything now works with the UI).

@lah7
Copy link
Member

lah7 commented Oct 9, 2016

@RetroEggy Similar, but not the same issue. Now that multi-device support has been implemented some time ago, it's now possible to detect keyboards and only disable FN and Space if they do not have the LEDs. This has been fixed in 763ffbc (for the next update).


@hhollenstain Is the key mappings still an issue under the new daemon (Polychromatic v.0.3.0 and later)?

@smevawala
Copy link

smevawala commented Oct 12, 2016

I can confirm the stealth issue is still happening with the newest polychromatic. (crap, nvm. actually just saw the dameon source was updated, I'm still using the ppa version of razer-drivers. Will test later tonight)

@lah7 lah7 added the openrazer Related to the OpenRazer backend (driver or daemon) label Oct 12, 2016
@lah7
Copy link
Member

lah7 commented Oct 13, 2016

I'm not entirely sure what's the issue exactly.... I'm thinking this is something at daemon level.

  1. Can the keys be selected from the UI, but do not light on the keyboard?
  2. Or, are the keys unable to be selected from the UI entirely? (Like nothing happens?)

@RetroEggy
Copy link

In my case, I'm not able to select the keys. I click space and nothing happens. Other keys work fine. When using a preset like static however, all keys including space and FN are affected.

@terricain
Copy link
Contributor

@lah7 you sure the space and fn are not disabled as I vaguely remember doing something like that

@lah7
Copy link
Member

lah7 commented Oct 15, 2016

I think we're crossing two separate issues here.

@RetroEggy @terrycain The inability to select FN/Space has been fixed (a new package hasn't been pushed out yet). This can be tested by installing the master version.

The original issue description sounds like a problem with the mappings (co-ordinates?):

but the F1 Key, the left arrow, enter, and z keys can't be mapped from the UI.

Which I'm assuming, when they're clicked in the editor, that key isn't lit up on the device. It could be a difference in US/UK layouts, or the wrong one is loaded in Polychromatic? Please could someone with a Razer Blade Stealth confirm if this is the problem?

@Bl4d3s
Copy link

Bl4d3s commented Mar 18, 2018

Its a bit old this issue, but I can confirm this as well. On my razer Blade stealth an entirely wrong keyboard mapping is loaded (looks like a balckwidow layout). I can select the keys and most light up correspondingly but some do not, and some light up other keys.
Here are some screenshots:
All yellow keys do not light up a key on my keyboard. The red ones are the arrow pad, the blue one is the windows logo, and the greens are the top row (but no f1).
Keys that do not work:
f1, alt, alt gr, right fn, right shift, enter (on a German Layout)

layout

mainwindow

@lah7
Copy link
Member

lah7 commented Mar 18, 2018

Thanks for confirming @Bl4d3s. At the moment, "application profiles" are really simple and all keyboards load this SVG (graphic). In future [eventually] there will be separate SVGs that can show the correct bindings for different locale layouts / devices.

@Bl4d3s
Copy link

Bl4d3s commented Mar 18, 2018

Okay, but still neither with the normal nor with the git version I can set all keys. Is there an easy way to fix it? I could maybe do some coding by myself if you point me in a direction.
Btw Im running Manjaro Linux

Edit: What I also noticed, I never got offered a choice to set the modes...

@lah7
Copy link
Member

lah7 commented Mar 18, 2018

Should be a relatively simple DIY fix for the time being: The SVG is located at /usr/share/polychromatic/mapping/blackwidow-chroma-keyboard-layout.svg - You can use a vector graphics editor like Inkscape to change these values in the XML Editor window/pane:

image

There's an onclick that tells it what co-ordinate to set it to.

To find out the co-ordinates, I have a script in my repository that will help: tools/step-through-matrix.py

Also, when saving, Inkscape does something with the file that means it won't work in Polychromatic again without first running tools/svg_editor.py -- that script assumes the file is at ../data/img/blackwidow-chroma-keyboard-layout.svg, you could tweak that path depending if you git clone this repo or edit it directly at /usr/share/...

Hopefully that should be a pointer in the right direction till this unstable stuff gets finished.. 👍

@Bl4d3s
Copy link

Bl4d3s commented Mar 19, 2018

One further question: I tried to run your script tools/step-through-matrix.py, but I keep getting this error:
./step-through-matrix.py Traceback (most recent call last): File "./step-through-matrix.py", line 7, in <module> import razer.client as rclient ModuleNotFoundError: No module named 'razer'
Any idea how to fix?

@lah7
Copy link
Member

lah7 commented Mar 19, 2018

Whoops, sorry, that should be:

import openrazer.client as rclient

The daemon was renamed some time ago - I must have missed a spot 🤨

@jramapuram
Copy link

Any chance we can get these changes merged? Having a missing 'z', 'alt', 'fn' and 'f1' are dimly lit 'Shift" + "Enter" are super annoying on a 1060 RB 2016

@lah7
Copy link
Member

lah7 commented Jun 23, 2018

Unfortunately not as-is, since the change will affect the SVG for all keyboards. The implementation to support per device is not there yet.

The unstable branch contains the future version where profiles will be remastered and will address issues like this (currently, that branch isn't ready). Please bear with me... it'll be sorted eventually!

For now, you can replace the SVG on your system with the one from the pull request.

@lah7 lah7 added this to the v1.0.0 milestone Feb 10, 2019
@lah7 lah7 added device map Adds or modifies a device graphic device specific Only affects specific hardware and removed openrazer Related to the OpenRazer backend (driver or daemon) labels May 23, 2020
@lah7 lah7 closed this as completed in bb9e51a Mar 19, 2021
@lah7
Copy link
Member

lah7 commented Mar 19, 2021

Good news! Your Blade Stealth 2016 models now have their own graphic!

🇬🇧
Screenshot_20210319_183900

🇺🇸
Screenshot_20210319_183926

@lah7 lah7 modified the milestones: v1.0.0, v0.6.1 Jun 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
device map Adds or modifies a device graphic device specific Only affects specific hardware feedback Opinion and thoughts to be taken on-board
Projects
None yet
Development

No branches or pull requests

7 participants