Skip to content
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

Cannot run the app on Windows 11 dark mode #109

Open
Alfex4936 opened this issue Apr 19, 2022 · 17 comments
Open

Cannot run the app on Windows 11 dark mode #109

Alfex4936 opened this issue Apr 19, 2022 · 17 comments
Labels
bug Something isn't working compile errors

Comments

@Alfex4936
Copy link

Just installed, tried to run the app but it gave me those errors.

image

windows11 (b22000) using dark mode in settings (Personalize - Color)

@Alfex4936 Alfex4936 added the bug Something isn't working label Apr 19, 2022
@im-coder-lg
Copy link
Member

Woah wth never seen that! I'll debug today and find the errors. Does the same happen when you run it directly from Python3.10?

@not-nef
Copy link
Member

not-nef commented Apr 19, 2022

looks like your theme files are corrupted

@im-coder-lg
Copy link
Member

Looks like the system can't read the images in the first place!

@rdbende
Copy link
Contributor

rdbende commented Apr 19, 2022

looks like your theme files are corrupted

Tk 8.5 gives this same error, when using png-s, since png support was only added in Tk 8.6. Probably this isn't the error, if TimerX was compiled with Tk 8.6, the exe should contain that version, but idk exactly how cx_freeze compiles python files.

@not-nef
Copy link
Member

not-nef commented Apr 19, 2022

Yeah we should switch to pyinstaller soon.

@Alfex4936
Copy link
Author

Woah wth never seen that! I'll debug today and find the errors. Does the same happen when you run it directly from Python3.10?

will try it later! but on my laptop using Windows 10 (dark mode)

the background is just transparent like this?

제목 없음

@im-coder-lg
Copy link
Member

That's normal. Switch to darkmode and restart the app via CLI, it would look better.

@Alfex4936
Copy link
Author

That's normal. Switch to darkmode and restart the app via CLI, it would look better.

Oh didnt know that option thanks! now it looks like this sadly

image

And if I set the timer for 1h 0m 0s, it just changes to default second when I hit play btn (setting like 1:33:0 works like 1:32:50)?

@im-coder-lg
Copy link
Member

Use it in system dark mode, it would look a lot more better ;)

@im-coder-lg
Copy link
Member

im-coder-lg commented Apr 20, 2022

It's the font colliding with the background, but hold up, the titlebar... Anyone know what that line of code is?

@im-coder-lg
Copy link
Member

But this is indeed a bug, we achieved this at compile-time, hence we either have to switch to PyInstaller, or fix cx_Freeze. Have YOu edited any code in setup.py? Could lead to mishaps.
Tagging this as compile error and adding to project to get resolved.

@im-coder-lg
Copy link
Member

We have plenty of time in the future since we have got holidays, so we'll try finding a potential bug fix at that time, it's best to investigate this for the time being. This deffo needs some team effort, so doing bug fixing in the holidays would be great since we can work simultaneously.

@sumeshir26
Copy link
Member

Well, No the background isnt supposed to be transperent, it should have acrillic on win10 and mica on win11.
@not-nef can you add the build.bat from Flux to TimerX?

@not-nef
Copy link
Member

not-nef commented Apr 20, 2022

Will do when i have time

@im-coder-lg
Copy link
Member

Well, No the background isnt supposed to be transperent, it should have acrillic on win10 and mica on win11.

Code errors for light mode bro

@not-nef can you add the build.bat from Flux to TimerX?

It better not be my kind of script to build TimerX! I made one and then we switched to cx_Freeze!

@im-coder-lg
Copy link
Member

You know, while rereading this, I found this:

And if I set the timer for 1h 0m 0s, it just changes to default second when I hit play btn (setting like 1:33:0 works like 1:32:50)?

It seems weird, but I don't know how the heck we could find that one line that disrupts this... Sorry to tell this really late, but I have vacations from tomorrow, so can't help at that time :( will try being updated though.

@sumeshir26
Copy link
Member

Ill fix the default sec thing by monday if nobodydoes it tell then

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working compile errors
Development

No branches or pull requests

5 participants