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

keybind's update_keyboard_mapping takes a long time to run in python3 #16

Open
inktrap opened this issue Sep 30, 2020 · 0 comments
Open

Comments

@inktrap
Copy link

inktrap commented Sep 30, 2020

Hi!

I did some work today to get pytyle3 and xpybutils to run on python3. Here are the results of what I did so far. This works mostly great!

There is one thing I don't get and even despite the fact that you stated a couple years ago that you don't want to work on xpybutil and pytyle3 anymore (we had some contact about this), I'll give it a shot; may you have an idea:

In xpybutil/keybind.py there is a check if there is a xproto.Mapping.Keyboard request. Then the keymap is updated. This update takes a long time to run and is very resource intensive. So much, that I can't use pytyle3. I added a return statement so the update is simply skipped.

I have the impression that this is run quite frequently and that other tilers do it too.

Why is it so costly? It is not supposed to take that long. When is this run? Any ideas how to fix this?

Thanks for the awesome work you did :) don't forget, pytyle3 has a clingy fanbase ;) <3

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

1 participant