Separate ray and firefish device names in PairSelectDeviceType.qml #464
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Attempt to address an issue where the ray and firefish devices do not appear in the pairing UI of Amazfish. It appears that ray and firefish were grouped together in PairSelectDeviceType.qml, whereas they are handled separately in devicefactory.cpp. This change separates the two devices in the UI, aligning with the handling observed in devicefactory.cpp. While untested, this adjustment aims to resolve the potential mismatch and allow proper pairing for ray and firefish.
|
Great that you test all AsteroidOS devices. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Attempt to address an issue where the ray and firefish devices do not appear in the pairing UI of Amazfish. It appears that ray and firefish were grouped together in PairSelectDeviceType.qml, whereas they are handled separately in devicefactory.cpp.
This change separates the two devices in the UI, aligning with the handling observed in devicefactory.cpp. While untested, this adjustment aims to resolve the potential mismatch and allow proper pairing for ray and firefish.