Sublime Text 3 Windows fixes: Updated the run() method to set cc.hwndOwner to None (temp fix) and added condition to only use color.decode('utf-8') in Sublime Text 2
The change to cc.hwndOwner is only a temporary fix to make it work on Windows without crashing Sublime Text 3.
I don't know enough about Windows programming or Python to know why it's crashing, but it works fine in Sublime Text 2 so I can only assume it's a problem with Sublime Text 3 itself at this point.
Of course setting the cc.hwndOwner to None does make Sublime Text 3 not respond if you click out of the colour picker because the cc.hwndOwner would usually prevent that from happening, but as soon as you exit the colour picker by closing it or choosing a colour Sublime will start responding again.
Sublime Text 3 Windows fixes: Updated the run() method to set cc.hwndOwner to None (temp fix) and added condition to only use color.decode('utf-8') in Sublime Text 2
The change to cc.hwndOwner is only a temporary fix to make it work on Windows without crashing Sublime Text 3.
I don't know enough about Windows programming or Python to know why it's crashing, but it works fine in Sublime Text 2 so I can only assume it's a problem with Sublime Text 3 itself at this point.
Of course setting the cc.hwndOwner to None does make Sublime Text 3 not respond if you click out of the colour picker because the cc.hwndOwner would usually prevent that from happening, but as soon as you exit the colour picker by closing it or choosing a colour Sublime will start responding again.