issue-221 add FEATURE_LV_FOCUS_BOX_AUTOHIDE to features list in 6D2 #223
+2
−0
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.
This is my first interaction/contribution to the project. So I had to configure my environment to have files to compile and to build a working ZIP.
The motivation to contribute to the project was the fact that Im the owner of 6D Mark II, and I want to have my LiveView with AF w/o unnecessary overlays on the screen.
I created an issue to track activity on a development #221 It basically explains that it would be nice to have a feature to hide a Focus Box while using a LiveView mode.
This will essentially help to achieve a Clean HDMI since the rest can be removed/cleared with INFO button (basic functionality).
Testing.
After compilation/packaging with
make -j6(actually I had to use a bit updated command because Im not allowed to modify/usr/binon a corp laptop)With slight modifications for

python3andgstatI managed to have it packaged w/o errors.Then with files generated in
build/zipI reinstalled build on Canon 6D2 and verified the functionality.IMG_2694.mov
On the top header I see the error message
EFLensComTask: stack warning: free=232 used=792which seems to be flaky appearing from time to time.I guess there could be a potential thread(s) optimisation needed. I will give more updates if it causes issues on longer use.