Closed MattDMo closed 2 years ago
Thanks for the report! Found the issue.
@gir-bot remove S: triage @gir-bot add T: bug, S: confirmed
This turned out to be an untested case when we switched to a more dynamic base Color object. ST Color Mod is the only custom plugin that overrides many of the guts of the color object to provide special handling of color mod syntax. We simply forgot to make sure it is comparing its type check against the dynamic base.
I have a local fix and will be in the next release. I may push a quick bugfix out tonight.
Fix was tagged, should be available in Package Control within an hour or two.
Description
Clicking on a color preview in a
.sublime-color-scheme
file doesn't allow you to change the color. The following traceback appears in the console:I've replicated this behavior in both macOS and Linux (running in a VM on the Mac) using Build 4134. I was also able to replicate it on the Mac in safe mode, after installing Package Control, ColorHelper, and PackageDev (needed b/c I'm working on a
.sublime-color-scheme
file).Very interestingly, I can't replicate it when working on a new CSS file:
Support Info
Steps to Reproduce Issue
Start Build 3134 in Safe Mode.
Install Package Control, then install ColorHelper and PackageDev.
Open
Neon.sublime-color-scheme
and wait for color previews to appear.Click on a color preview, such as the one in the top
"variables"
section next to the final variable"pink"
.Click on
Picker
to open the color picker (Mac), or just click on the pink box (Linux).Click on any color you like in the color picker, then click on the Select button.
The original color
#FF01C3
will not change, and the traceback above will appear in the console. The window with all the insert buttons does not appear.I'm using the default preferences in Safe Mode.