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

Ranges of same RPC parameters in MOBILE_API and HMI_API are not unify. #261

Open
Yuki-Shoda-Nexty opened this issue Jun 16, 2020 · 0 comments

Comments

@Yuki-Shoda-Nexty
Copy link

We propose correcting the range of some parameters that are defined in both HMI_API.xml and MOBILE_API.xml but each has defferent ranges.

In current HMI_API.xml and MOBILE_API.xml, there are some parameters that are used in both xml but each has defferent ranges.
By unifying such ranges, we can provide more accurate RPC documents for SDL developers.
The target items are described in the Excel file.

mismatch of range.xlsx

e.g. The parameter ts of RPC TouchEvent, same parameter is defined both MOBILE_API.xml and HMI_API.xml, but its 'maxvalue' is defferent. Therefore modify the value of maxvalue like below

To unify the maxvalue in both xml, modify the maxvalue of ts in HMI_API.xml like below.

-   <param name="ts" type="Integer" mandatory="true" array="true" minvalue="0" maxvalue="2147483647" minsize="1" maxsize="1000">
+   <param name="ts" type="Integer" mandatory="true" array="true" minvalue="0" maxvalue="2000000000" minsize="1" maxsize="1000">
        <description>
        The time that the touch was recorded.  This number can the time since the beginning of the session or something else as long as the units are in milliseconds.
        The timestamp is used to determined the rate of change of position of a touch.
        The application also uses the time to verify whether two touches, with different ids, are part of a single action by the user.
        If there is only a single timestamp in this array, it is the same for every coordinate in the coordinates array.
        </description>
    </param>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant