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.
Hello,
See my proposed PR concerning CustomWatchface code
I will be honest I didn't test it (didn't install your PR in my loop phone)
=> Your latest proposal was quite closed to mine but with missing items:
ResFileMap.kt
), so CustomWatchfaces with different images (Background.png, BackgroundHigh.png, BackgroundLow.png CoverChart.png, ...), you can now also include BachgroundVeryHigh.png and BackgroundVeryLow.png, ...) to manage CWF. For testing hardcoded filename, you can update Blue Ring watchface (Simon 7.zip file) or P-Zero watchface (both should have a yellow background image for High and red background image for low, so with adding copy of these files with VeryHigh and Verylow it should work)There is one remaining topic which could be discussed: Within
setWatchfaceStyle
, when I initialized veryHighColor and veryLowColor values, I put as default highColor and lowColor-> All v1 and v2 will not have these keys within their json file included in CWF, so with my code nothing change within their watchfaces
With your proposal they will have with missing keys
ContextCompat.getColor(this, R.color.dark_veryHighColor)
so the default veryHigh color and the default veryLow Color.On my side I prefer keep it unchanged (and explain how to update an existng CWF V1 or V2 to include the 2 new veryHigh and verylow keys to update it) because with your proposal, the veryHigh will be visible (default high color is Yellow), but not veryLow (same color than current Low)