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

Update Glutin #234

Closed
rigtorp opened this issue Jan 8, 2017 · 14 comments
Closed

Update Glutin #234

rigtorp opened this issue Jan 8, 2017 · 14 comments

Comments

@rigtorp
Copy link

rigtorp commented Jan 8, 2017

This version of glutin doesn't compile on Windows 10:

[dependencies.glutin]
git = "https://github.com/jwilm/glutin"
rev = "af7fe340bd4a2af53ea521defcb4f377cdc588cf"

Upstream glutin 0.7.1 compiles fine:

glutin = "0.7.1"

This is blocking windows support.

@insunaa
Copy link

insunaa commented Jan 8, 2017

Have you tried compiling alacritty with glutin 0.7.1? I'm curious what your results are

@jwilm
Copy link
Contributor

jwilm commented Jan 8, 2017

Have you tried compiling alacritty with glutin 0.7.1? I'm curious what your results are

This will not work. Alacritty is on a fork of glutin that has a very different Event::KeyboardInput variant:

  • Includes Mods which are the modifier keys as provided by the XEvent or equivalent on other platforms
  • Includes the UTF-8 string generated by the input sequence. This is normally provided in a separate event, but Alacritty needs both at once to either run a key binding or forward the string to the pty.

@rigtorp
Copy link
Author

rigtorp commented Jan 8, 2017

@jwilm Does it make sense to upstream your changes to glutin?

@jwilm
Copy link
Contributor

jwilm commented Jan 8, 2017

Very much so. I was hoping to make these changes for windows and wayland before opening a PR, but maybe they would be accepted separately.

@jwilm jwilm changed the title Version of glutin used by alacritty doesn't compile on Windows 10 Update Glutin Jan 9, 2017
@jwilm
Copy link
Contributor

jwilm commented Jan 9, 2017

Renamed this issue to suggest an action. We need to reapply my patches on top of what's now two projects (winit + glutin), upstream them, and then update Alacritty's dependencies.

@rigtorp
Copy link
Author

rigtorp commented Jan 11, 2017

Opened this issue rust-windowing/winit#108 to see if upstream is willing to accept these improvements.

@rigtorp
Copy link
Author

rigtorp commented Jan 18, 2017

Submitted PR rust-windowing/winit#112 to add keyboard modifiers to winit keyboard event.

@emersion
Copy link

emersion commented Mar 2, 2017

rust-windowing/winit#112 has been merged

@rigtorp
Copy link
Author

rigtorp commented Mar 3, 2017

@emersion Now we need to update glutin to this newer version of winit

@mystal
Copy link
Contributor

mystal commented Apr 27, 2017

Looks like with the merge of rust-windowing/glutin#864 glutin's master branch is now using the latest winit. One step closer!

@emersion
Copy link

Linking a related PR: #554

@jonhoo
Copy link
Contributor

jonhoo commented Jul 2, 2017

I wonder if this would also fix #148...

@jwilm
Copy link
Contributor

jwilm commented Jul 2, 2017

It might; there's been a lot of work in this area in winit lately. There's also someone waiting to contribute some fixes for IME support which might be the fix needed for compose key.

@jwilm
Copy link
Contributor

jwilm commented Jul 2, 2017

Glutin/winit API churn is really high right now, and the latest candidate branch has some bugs. There's a new WIP to update current Glutin API to winit 0.7.1, and hopefully we can get on that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

6 participants