murarth on master
Fix broken link in documentatio… (compare)
kchibisov on v0.26.0
kchibisov on master
Release version 0.26.0 (compare)
kchibisov on master
Usa stable version of rustfmt f… (compare)
UndeadLeech on FreenodeYou can't just make another release for a cross-platform window toolkit and then remove half the platforms in a release.
furiouzzWell I am fine. Very interested by rust ecosystem and rust people. I want to help =)
UndeadLeech on FreenodeThat's great to hear. I'm not super familiar with winit's issue tracker, but if you're willing to learn and help, have you considered picking an easy issues and trying your hand at it?
furiouzzI got a background of web developer, I supposed I could handle the Gamepad issue here rust-windowing/winit#944
UndeadLeech on FreenodeSince Windows is already implemented, I'm sure you could try your hand at one of the other platforms using that as reference. Though it's not marked as
easy, which might mean that it could be difficult for someone completely new to systems languages. But web developer != web developer, so it's hard to say for sure.
LevansI expect the difficulty of this issue to be mostly in the fact that every OS has a different API for handling gamepads.
furiouzzEvery cross-platform project are kind of plumbing haha
UndeadLeech on FreenodeIt seems like
Noneis equal to
est31 on Freenodegood point
est31 on Freenodebut even then you can have an LTS that you accept bugfixes for and some experimental but proper releases with removed support
UndeadLeech on FreenodeI've considered this myself before and I don't think it would be acceptable to make any official release that removes support for a platform that was previously working just fine.
UndeadLeech on FreenodeThat's a massive red flag imho, while pre-releases are just fine.
heeen on Freenodecan someone help me with the two fixmes here https://gist.github.com/heeen/9e36b28f4251a84c5f1a1411044231a2
heeen on Freenodethis is adapted from ash's example code
UndeadLeech on FreenodeThe
borrow_mut()looks problematic. Have you tried without that?
heeen on Freenodeuhm
heeen on Freenodeevent_loop is of type RefCell<EventLoop>
heeen on Freenodeit doe snot have run
heeen on Freenodeno?
UndeadLeech on FreenodeOh, sorry. I expected the event loop to be owned.
UndeadLeech on FreenodeWhich raises the question, why is it not?
heeen on Freenodemaybe it could be owned
UndeadLeech on FreenodeI'd assume that would fix the error.
heeen on FreenodeI don't know. I'm a rust beginner, really, coming from c++
UndeadLeech on FreenodeTry removing the
RefCellin the event_loop struct type and then the
UndeadLeech on FreenodeThen it should work.
heeen on Freenodebecause at older winit was just not delivering window events in time or at all
UndeadLeech on FreenodeI'm not sure who ash is.
UndeadLeech on FreenodeUnless you're talking about pokemon that is.
heeen on Freenodeok, that seems to work so far. not sure if the full example will still work though.
heeen on Freenodethanks.
heeen on Freenodethe second fixme is about the F parameter not living long enough
heeen on Freenodeshould it be +'static?
UndeadLeech on FreenodeI don't see why it wouldn't.
UndeadLeech on FreenodeBy which I mean I don't immediately see why the events_loop is in a refcell in the example.
heeen on Freenodeactually, no it does not work
heeen on Freenodeannot move out of
self.event_loopwhich is behind a shared reference
heeen on Freenodewithout the refcell