[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] qapi/ui: Fix documentation of upper bound value in InputMove
From: |
Markus Armbruster |
Subject: |
Re: [PATCH] qapi/ui: Fix documentation of upper bound value in InputMoveEvent |
Date: |
Thu, 16 Jan 2025 14:51:49 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Zhang Boyang <zhangboyang.id@gmail.com> writes:
> On 2025/1/16 20:40, Markus Armbruster wrote:
>> Zhang Boyang <zhangboyang.id@gmail.com> writes:
>>
>>> The upper bound of pointer position in InputMoveEvent should be 0x7fff,
>>> according to INPUT_EVENT_ABS_MAX.
>>>
>>> Signed-off-by: Zhang Boyang <zhangboyang.id@gmail.com>
>>> ---
>>> qapi/ui.json | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/qapi/ui.json b/qapi/ui.json
>>> index 460a26b981..7b18662018 100644
>>> --- a/qapi/ui.json
>>> +++ b/qapi/ui.json
>>> @@ -1133,7 +1133,7 @@
>>> # @axis: Which axis is referenced by @value.
>>> #
>>> # @value: Pointer position. For absolute coordinates the valid range
>>> -# is 0 -> 0x7ffff
>>> +# is 0 -> 0x7fff
>>
>> Opportunity to replace "->" by "to" or "..". If you agree, I'll squash
>> that into your patch in my tree.
>>
>
> OK, Thank you :)
>
> Zhang Boyang
Queued. Thanks!
[...]