Sergey Khodych wrote:
>> To reply to myself. I've missed the fact that if the requested format
>> is the
>> same as Wine's internal format it will be a simple memcpy. I did not
>> want to
>> penalize most dinput applications that just use default keyboard
>> format (array
>> of 256 bytes).
>>
>
> To reply to myself. I've missed the fact that if the requested format is
> the
> same as Wine's internal format it will be a simple memcpy. I did not
> want to
> penalize most dinput applications that just use default keyboard format
> (array
> of 256 bytes).
>
What do you think about using c
Vitaliy Margolen wrote:
> Sergey Khodych wrote:
>>> Any particular reason for this? Do you have a program that sets different
>>> data format? The reason I ask - copying 256 bytes is much faster then
>>> iterating over the whole data format and copying one byte at a time.
>>>
>> A possibility of
Sergey Khodych wrote:
>> Any particular reason for this? Do you have a program that sets different
>> data format? The reason I ask - copying 256 bytes is much faster then
>> iterating over the whole data format and copying one byte at a time.
>>
> A possibility of using custom data format, for a
A possibility of using custom data format, for any type of devices, is
described in DirectX SDK documentation.
For example Monolith's F.E.A.R. use this method.
> Any particular reason for this? Do you have a program that sets different
> data format? The reason I ask - copying 256 bytes is much
Sergey Khodych wrote:
>
>
>
Any particular reason for this? Do you have a program that sets different
data format? The reason I ask - copying 256 bytes is much faster then
iterating over the whole data format and copying one byte at a time.
Vitaliy.
