You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the matching conditions of a keyboard definition are the following:
(1) Search keyboard definitions from the Firestore database with a combination of "Vendor ID" and "Product ID".
(2) If the number of the result of (1) is a single, use the keyboard definition as the result of the matching.
(3) If the number of the result of (1) is multiple, furthermore search a keyboard definition with "PRODUCT" string from the result. If exists, use the keyboard definition as the result of the matching.
When importing a JSON file from a user's local environment, and there is same combination of vendor ID and product ID in the database, the current version of Remap has an issue to return different keyboard definition because of without doing matching the PRODUCT string.
We should improve the 2nd condition to add a PRODUCT string as a matching rule.
The text was updated successfully, but these errors were encountered:
Due to #600, Corne keyboard cannot be detected with VID and PID combination only. This is a big problem. Basically, all keyboards should be able to be detected with VID and PID only. According to this policy, the #600 should be reverted.
Currently, the matching conditions of a keyboard definition are the following:
(1) Search keyboard definitions from the Firestore database with a combination of "Vendor ID" and "Product ID".
(2) If the number of the result of (1) is a single, use the keyboard definition as the result of the matching.
(3) If the number of the result of (1) is multiple, furthermore search a keyboard definition with "PRODUCT" string from the result. If exists, use the keyboard definition as the result of the matching.
When importing a JSON file from a user's local environment, and there is same combination of vendor ID and product ID in the database, the current version of Remap has an issue to return different keyboard definition because of without doing matching the PRODUCT string.
We should improve the 2nd condition to add a PRODUCT string as a matching rule.
The text was updated successfully, but these errors were encountered: