scottclowe / matlab-schemer

Apply and save color schemes in MATLAB with ease.
BSD 2-Clause "Simplified" License
1.19k stars 273 forks source link

Wrong background color on selected variables after restoring schemes #11

Closed LoGGoL closed 8 years ago

LoGGoL commented 8 years ago

Hi, I observe another issue with the matlab_schemer. image

This happens, when I export my current scheme, load another scheme from the scheme folder and then restore my saved scheme back. Also the M-Lint hints on the right side are black and not orange.

Regards,

scottclowe commented 8 years ago

Hi @LoGGoL,

I was not able to reproduce the bug.

It seems that schemer_export has erroneously outputted black for the M-Lint background and warning colours.

If this is correct, the exported scheme will contain these lines:

Colors_M_Warnings=C-16777216
ColorsMLintAutoFixBackground=C-16777216

The reason will be because unassigned colours (colours which have never been changed from the default since installing MATLAB) are returned as black when using the function to fetch the preference colour - com.mathworks.services.Prefs.getColorPref. As far as I have been able to ascertain, there is no way of telling whether a specific colour is unassigned or genuinely is black.

Currently, the only solution is to ensure every colour is assigned by manually setting every colour (even if it setting it to be the same as the default value, this still works). This is described in the help for schemer_export.

If not, could you try this and see if it resolves the issue?

scottclowe commented 8 years ago

This error should not have been possible since version v1.2.1, which introduced [checks for each preference panel to ensure the values have been set before exporting them].(https://github.com/scottclowe/matlab-schemer/commit/0bb4e679a10af83d8ebedb32e5551aabd37985f3)

Consequently, I do not understand how this issue has arisen. Without additional details on how to produce this error, I am unfortunately forced to close this bug with the issue unresolved.

If anyone experiences this bug again, please reopen this issue.