-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Wrong icons on Windows? #25
Comments
Actually, it seems to be a bug with Windows install step? When I first pressed Install, I could see Unavailable icon being applied correctly, but for some reason it's displaying on "(None)" style. When I change it to the actual Breeze style, to be able to apply it, Unavailable icon and everything else below become wrong. Here's a recording, https://drive.usercontent.google.com/download?id=1q0ROm-hvEG2ypIlGaTi3da06ZFbQ_tDF&authuser=0 UPDATE: I managed to get it to work by explicitly using the Save As button, in the automatically opened Control Panel window, then manually naming it as the intended name, to overwrite the wrongly configured scheme. Only then will I end up with a properly configured scheme. Very odd. UPDATE 2: Never mind. It would actually just make the new scheme inherit default Unavailable icon. Diagonal select 1 & 2 also seemed to use default instead. Windows is whack. In the end I just manually edited the scheme... |
The build configuration is wrong and there were accidentally cursors added which are not available on windows. E.g. zoom in, zoom out, etc. |
Addressing this issue. Refer to #30 for updates. |
@ful1e5 Any plan to push another release build? |
@BobbyWibowo Inshallah soon. |
Hi there, for some reason the latest update, v2.0.1, seem to register wrong icons starting from Unavailable icon to everything else below.
Normal select icon until Handwriting icon do appear to be correct.
I can confirm the same thing happened for all 9 variants (black/dark/light and their respective R/L/XL sizes).
I also made sure I uninstalled the old versions prior to installing the new versions.
The text was updated successfully, but these errors were encountered: