-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
02.11.2011 06:05, Vitaliy Margolen wrote:
> If you really want it to get in just do it via DI. Use old patches and
> projects like x360ce for ideas, code, and documentation. Too bad x360ce is
> in c#.
>
x360ce XInput1_3.dll implementation is written
I've got a general question about the Windows subsystem I'm a bit interested
of and considering spending some time trying to implement it. What I'm talking
about is "new" input handling API MS positions as the DirectInput successor:
XInput 1.x.
If you really want it to get in just do it via DI. Us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
01.11.2011 21:12, Austin English wrote:
> Some patches: ...
>
> And discussions: ...
Austin, thanks for posting these links. I've seen patches by Andrew posted in
October, 2008 and the initial discussion that followed those postings to the
list when
* On Wed, 2 Nov 2011, Alexey Loukianov wrote:
> 01.11.2011 18:54, Jerome Leclanche wrote:
> >
> > I'm no expert in any *input* API, but it sounds like it would be better to
> > reimplement dinput under the xinput api; similarly to how audio has been
> > handled.
>
> Despite being more recent API X
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
01.11.2011 19:23, GOUJON Alexandre wrote:
> On 11/01/2011 03:11 PM, Alexey Loukianov wrote:
>> a) [...] What I've got available to do the tests are three Windows-based
>> PCs
> You should have a look at https://testbot.winehq.org/ which let you submit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
01.11.2011 18:54, Jerome Leclanche wrote:
>
> I'm no expert in any *input* API, but it sounds like it would be better to
> reimplement dinput under the xinput api; similarly to how audio has been
> handled.
Despite being more recent API XInput actuall
On Tue, Nov 1, 2011 at 00:47, Alexey Loukianov wrote:
> What I'm interested in (and that's is the reason I'm posting to devlist) is
> what are the plans on real implementation of MS XInput API? Are there anybody
> working on topic? Were there any preliminary patches floating around aimed at
> impl
On 11/01/2011 03:11 PM, Alexey Loukianov wrote:
a) [...] What I've got available to do the tests are three Windows-based PCs
You should have a look at https://testbot.winehq.org/ which let you
submit a patch on several (VMware'd) Windows machines.
But I doubt there is any input devices in these
On Tue, Nov 1, 2011 at 2:11 PM, Alexey Loukianov wrote:
> d) Code duplication issues. XInput API mirrors DirectInput API at some part
> and
> it might be reasonable to re-use code parts from the existing DirectInput
> linux
> event-based joystick driver. I am thinking about implementing XInput o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
01.11.2011 11:58, Dan Kegel wrote:
> Hi, I doubt anyone's working on it (would like to be wrong about that).
> Things to keep in mind: ...
Dan, thanks for a quick answer on topic. Besides these general and very valuable
keypoints there are some other
Hi,
I doubt anyone's working on it (would like to be wrong about that).
Things to keep in mind:
- contributing test cases is good
- looking at Microsoft code, even watching traces with Process
Monitor, is bad and can get your code rejected
- so contributing test cases is very good. blackbox testin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Good day to all,
I've got a general question about the Windows subsystem I'm a bit interested
of and considering spending some time trying to implement it. What I'm talking
about is "new" input handling API MS positions as the DirectInput successor:
X
12 matches
Mail list logo
