-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix a bug related to the alpha hex calculation #1048
Conversation
Not sure if I should add this comment or not: |
Well, the behavior is different this time. Rather than starting with an all white background, it looks normal until a reload, which might be what this fixes for me. Unfortunately transparency doesn't work at all now. I'm running the default config with only the following
Well it was worth a try 😄 |
Wait wait, apparently this only seems to be a problem when running in dev mode. Also, it looks like After a bit more playing around, doing a full reload sets the transparency to |
This seems to fix (the more important) half of the issue. I'll make a new issue on the remaining problem with |
Please can someone review this? I've been having the same problem on Windows 10 x64, Hyper 1.0.0. |
Not exactly sure who has write access to this project, but looking at some recently merged PRs, @rauchg seems to. Would you mind taking a look over this and merging it? Thanks! |
Can you rebase to latest master? @dkniffin |
bac9962
to
cda7544
Compare
@ppot Done. |
I was running into an issue on OSX, where I'd set the backgroundColor to something like
'rgba(0, 0, 0, 0.8)'
, and everything would look great, until I closed Hyper, and re-opened it. Once I did that, it would still have transparency, but it'd be more transparent.I tracked this down to the change I made. Basically, what was being done before is
0.8
would be converted to the decimal number 80, which is not correct. What should happen is that0.8
should be a percentage of 100% opacity, which is 255, then converted to a hex string (viatoString(16)
). Hopefully that makes sense.I'm not 100% sure, but I think this might also resolve #873, but I'd need @Lindenk to confirm.