The only alternative to System.Drawing.Color built on actual color theory
Overview
Why KtColor Exists
Core Concepts
1. Color Representation
2. Three Color Types
Palette System
Base Colors (Neutrals)
Accent Colors (Main Palette)
Theme Variables
Shade System
String Format Support
Parsing Formats
Rendering Formats
Operators Reference
Implicit Conversions
Lightness Operations
Opacity Operations
Color Inversion
Conditional Operations
Color Mixing
Comparison
Boolean Context
Property Inspection
Color Properties
State Checks
Theme System
Setting Theme Variables
Theme Change Events
Default Theme Colors
Advanced Features
Content Color Calculation
Opaque Color Blending
Color Iteration
Random Colors
Design Decisions
Why HSL over RGB?
Why String-Based Palette Names?
Why Variable System?
Why Operator Overloading?
Performance Considerations
Lazy Evaluation
Theme Variable Invalidation
Allocation Patterns
Integration Patterns
PropertyGrid Support
Custom Editor
JSON Serialization
Migration Guide
From System.Drawing.Color
From String Color Names
Adding Theme Support
Best Practices
1. Use Theme Variables for Semantic Colors
2. Store KtColor, Render Late
3. Use Operators for Variations
4. Leverage Content Colors
5. Subscribe to Theme Changes
Common Pitfalls
1. Comparing Rendered Colors
2. Losing Shade Information
3. Not Handling Empty Colors
4. Ignoring Opacity in Rendering
API Summary
Static Properties
Instance Properties
Static Methods
Instance Methods
Operators
Last updated

