Improve accessibility of file browser items #929
Closed
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.
More info in the commit message as usual.
I guess the main point of discussion here is where the appropriate code belongs - whether or not it is right to set the
representedObject
ofOFBPathInfoCell
to the relevant FSItem and use this information inside the
OFBPathInfoCell
accessibility support (this is the way I did it as I feltOFBPathInfoCell
should know its accessibility since it could be used in more than one place, like File Chooser, which, however, does not seem to reflect this accessibility support as it has its own logic to determine file attributes), or whether to set the accessibility attributes as override values in
[FSOutlineViewDelegate willDisplayCell:...]
.These patches are released to public domain by my employer, BRAILCOM,o.p.s.