Fix EcoBraille and Lilly braille display drivers #17635
Open
+14
−5
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.
Link to issue number:
Fixes #17502
Summary of the issue:
In #15386, support was added for numRows and numCols on braille displays. Setting numCells explicitly would also set numCols.
In #17011, we're much more relying on numCols and numRows.
For the eco braille and Lilli drivers, numCells was implemented by overriding _get_numCells. However this way, the setter of numCells would never be called and therefore numCols would always be 0.
Description of user facing changes
Fix braille for Eco Braille and Lilli displays.
Description of development approach
[(0, 0)]
instead of[(0, 1)]
. The latter suggests that the window contains one cell, which is not the case. @michaelDCurran you might want to check this.Testing strategy:
@dreinn Could you test this?
Known issues with pull request:
I think we should consider a long term strategy for
numCells
vs.numRows
/numCols
. We still need to account for both now, which isn't ideal and could easily go wrong as proved.Code Review Checklist:
@coderabbitai summary