fixed name collision for keyword NONE #9
Merged
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.
Embarrassingly,
NONE
enum collides with anotherNONE
enum defined in ezTime.Namespaces. Yeah.
Also, I'm a bit frustrated that Meshtastics has a fixed dependency on this oled lib even though I'm not using any oleds: I'm using a TFT display and LovyanGFX (not me but rather you in the Meshtastic display code). More bugs, more code, more space...