Skip to content

Releases: facelessuser/ColorHelper

ST3 6.2.1

03 Jul 13:35

Choose a tag to compare

6.2.1

  • FIX: Fix issue where recent changes for "on activated" caused
    a regression.

ST3 6.2.0

30 Jun 01:07
27f770c

Choose a tag to compare

6.2.0

  • NEW: Since browsers do not and may not introduce Color Level 4
    gamut mapping until some future spec, make gamut mapping approach
    configurable. Use clipping by default to match browsers as this is
    likely what people expect even if it is not an ideal approach. Use
    gamut_map in settings option to manually control the approach.
  • NEW: Upgrade ColorAide to 2.4.
  • NEW: Previews now run immediately on view activation.
  • NEW: The sliding preview window has configurable padding to scan
    a larger region.
  • FIX: Fix regression where contrast logic could not adjust to a
    given contrast due to a property access.

ST3 6.1.1

01 Feb 14:18

Choose a tag to compare

6.1.1

  • FIX: Fix broken gamut mapping logic after recent port of latest
    coloraide.

ST3 6.1.0

18 Jan 02:39

Choose a tag to compare

6.1.0

  • NEW: Update to ColorAide 1.5.
  • FIX: Fix issue where if a view does not have a syntax it could
    cause an exception.

ST3 6.0.3

12 Aug 02:04

Choose a tag to compare

6.0.3

  • FIX: Fix registration of color spaces in custom color objects.

ST3 6.0.2

10 Aug 01:17

Choose a tag to compare

6.0.2

  • FIX: Fix issue where default, dynamic color class wasn't always
    properly.

st3-6.0.1

09 Aug 12:21

Choose a tag to compare

6.0.1

  • FIX: Fix absolute import reference that should have been relative.

ST3 6.0.0

08 Aug 17:32

Choose a tag to compare

6.0.0

WARNING: We finally made it to a stable coloraide 1.x.x release,
but some more unforeseen changes had to be made. This has been a long
road to get the underlying color library to a stable state.

  • User created custom plugins may need refactoring again, but most
    should be unaffected.
  • If you tweaked the newadd_to_default_spaces, please compare against
    the default list as some plugins were renamed and user settings may
    need to get updated. Color space plugins that do not properly load
    should show log entries in the console.
  • NEW: Upgraded to the stable coloraide 1.1. This should hopefully
    eliminate API churn as it is now a stable release.
  • NEW: Log when default color space loading fails.
  • FIX: Fix color picker slider issue.

ST3 5.0.1

03 Aug 01:30

Choose a tag to compare

5.0.1

  • FIX: Fix issue with Sublime ColorMod.

ST3 5.0.0

13 Jul 03:26

Choose a tag to compare

5.0.0

BREAKING CHANGE: Newest coloraide was updated. It is approaching
a 1.0 release. In the path to a 1.0 release some refactoring and
reworking caused custom color classes to break. All internal color
classes should be fine, but any users that created custom local
color classes will need to update the color classes and color spaces
to work with the latest version.

  • NEW: Upgrade to latest coloraide.
  • NEW: Many new color spaces have been added and can optionally
    be included via the new add_to_default_spaces option. Some that
    were available previously are no longer registered by default.
    See add_to_default_spaces in the settings file to enable more
    spaces. A restart of Sublime Text is required when changing this
    setting.
  • NEW: Add new add_to_default_spaces which allows a user to add
    NEW color spaces to the default color space so that the new spaces
    can be saved and recognized in palettes and other areas of ColorHelper.
    Modifying this setting requires a restart of Sublime Text. Custom
    color classes should only be used to modifying previously added
    color spaces to add to recognized input and output formats.