Open Defman21 opened 7 years ago
Doesn't look like this affects the color scheme in any way, it just is missing the warning so the user doesnt know what's going on.
Doesn't look like this affects the color scheme in any way, it just is missing the warning so the user doesnt know what's going on.
What do you mean? If the CSS isn't saving then it definitely effects the colour scheme.
How does it not saving affect the color scheme
It doesn't affect the default color scheme, Carey. It won't break the scheme or something, the problem is in the UX. Komodo should ask for a fork of the scheme when the user edits its CSS so the changes won't lost.
If it's in the same dialog and they save at the same time i would consider the CSS as part of the colour scheme so in that sense, the color scheme is broken if I can't save it. I guess you guys mean the dialog is broken. Same diff.
We all agree on the solution to fix it, so ya...
Short Summary
When you want to edit a built-in scheme, you have to fork it (Komodo will ask for it). However, this does not happen when you simply change its CSS.
Platform Information
Komodo Edit or IDE? IDE Komodo Version? latest nightly Operating System (and version)? elementary OS 0.4