Skip to content
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

New Theme Colour Structure. Replacing hard coded colours in IDE with variables #1153

Open
wants to merge 24 commits into
base: master
Choose a base branch
from

Conversation

SteveSmithSoftware
Copy link

Added GetNames, GetValues and Count methods

Added GetNames, GetValues and Count methods
Additional Type Checking
Base structure for new IDE Colour handling. Will allow for multiple Colour sections in the theme.toml file
Part of the project to replace all hard coded colours in the IDE with variables
This implements the new Theme Colour structure on top of the existing structure. This is to minimise the number of code changes in one commit
…eColours

New Theme Colour Structure. Part I
@SteveSmithSoftware SteveSmithSoftware changed the title Update Enum.bf New Theme Colour Structure. Part I Oct 4, 2021
SteveSmithSoftware and others added 12 commits October 4, 2021 20:08
Use Default Colours when no Theme specified
No need to Set defaults. Handled in ThemeColors
Split Colors into Colors & Theme
Replace DarkTheme.COLOR_... with ThemeColors.Theme..Color
Removed separate color array and replaced with reference to ThemeColors static array element
The vast majority of hard coded colours have been replaced with variables. Refer to Beefy2D/src//theme/ThemeColors.bf
@SteveSmithSoftware SteveSmithSoftware changed the title New Theme Colour Structure. Part I New Theme Colour Structure. Replacing hard coded colours in IDE with variables Oct 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant