summaryrefslogtreecommitdiff
path: root/tests
diff options
context:
space:
mode:
authorHugo Locurcio <hugo.locurcio@hugo.pro>2020-11-03 00:21:06 +0100
committerAaron Franke <arnfranke@yahoo.com>2020-11-03 04:46:08 -0500
commit7adb6b91b33e297b4833ef5f82adcf64a15777f4 (patch)
tree8a47d75e5a7ea66f1b5deec162408887090cdd11 /tests
parent873d4617852cddfd368e3046f718f410eade6a3e (diff)
Remove `Color.contrasted()` as its behavior is barely useful
Returning the most contrasting color isn't a trivial task, as there are often many possible choices. It's usually best left for the user to implement using a script.
Diffstat (limited to 'tests')
-rw-r--r--tests/test_color.h3
1 files changed, 0 insertions, 3 deletions
diff --git a/tests/test_color.h b/tests/test_color.h
index dfdc29ec7d..e5b6899908 100644
--- a/tests/test_color.h
+++ b/tests/test_color.h
@@ -185,9 +185,6 @@ TEST_CASE("[Color] Manipulation methods") {
CHECK_MESSAGE(
blue.inverted().is_equal_approx(Color(1, 1, 0, 0.4)),
"Inverted color should have its red, green and blue components inverted.");
- CHECK_MESSAGE(
- blue.contrasted().is_equal_approx(Color(0.5, 0.5, 0.5, 0.4)),
- "Contrasted pure blue should be fully gray.");
const Color purple = Color(0.5, 0.2, 0.5, 0.25);