-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Color scheme configuration #20
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Fixed a bug where color background was not reset properly; * Fixed a bug where font intensity was not reset properly; * Changed internal commands to color background and text;
* User may now get and set text and background colors used by the message logger for different message types and tags; * Added a default color (DFLT) to the Colors enum; * Refactored some color resetting internal functions and implementations (without breaking backward compatability); * Minor changes to variable names, comments and code structures;
* Setter functions for logger colors now receive a pointer for the display colors. This avoids unnecessary struct duplication. Due to this, added changes necessary for pointer handling in setter functions; * Added thread-safety checks to setter functions;
* Changed an error message to match other messages of the same kind; * Changed a color used in an example to improve aesthetics;
* User may now get and set text and background colors used by the message logger for different message types and tags; * Added a default color (DFLT) to the Colors enum; * Refactored some color resetting internal functions and implementations (without breaking backward compatability); * Minor changes to variable names, comments and code structures;
* Setter functions for logger colors now receive a pointer for the display colors. This avoids unnecessary struct duplication. Due to this, added changes necessary for pointer handling in setter functions; * Added thread-safety checks to setter functions;
* Changed an error message to match other messages of the same kind; * Changed a color used in an example to improve aesthetics;
…anjeira/C-MessageLogger into 011_color_scheme_config
* Created macros to house the default message and tag colors for the logger. This allows reusability by my module and the user; * Changed the logger color pallet to be a static variable;
* Added functionality to reset the logger colors, with an example in the sample; * Added the const modifier to the origin DisplayColors in the copy_display_colors function; * Updated README.md to reflect this new feature;
* Because this function is always called before a tag or message being printed inside a locked component, there is no reason to reset the colors only to them assign different colors to the output.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #11.