✔️ Deploy Preview for timerx-app canceled.

🔨 Explore the source changes: 35aa821

🔍 Inspect the deploy log: https://app.netlify.com/sites/timerx-app/deploys/61e192890f6250000848ab6e

Any toggle for that though?

Wait I'll try activating checks for macOS and Linux.

Can you try opening a Gitpod env and test it? Also try testing the same on your Mac Mini. But don't use your dad's Mac Mini.
I expect you have Git and Python 3.8+ on your Mac mini, so try these steps:

git clone https://github.com/sumeshir26/TimerX.git
cd TimerX
git checkout Blur
git fetch && git pull
pip install -r requirements.txt
python main.py

Check the TimerX console on Gitpod for the error. I will test on my RasPi soon, kinda busy.

@not-nef This is definitely not intended LOL 😂:-

FYI, OS in Dark Mode, TimerX in Light

lol that's abnormal

@not-nef This is definitely not intended LOL 😂:-

FYI, OS in Dark Mode, TimerX in Light

Well no it isnt lmao

Wait I'll try activating checks for macOS and Linux.

It literally did checks for macos

Can you try opening a Gitpod env and test it? Also try testing the same on your Mac Mini. But don't use your dad's Mac Mini.
I expect you have Git and Python 3.8+ on your Mac mini, so try these steps:

git clone https://github.com/sumeshir26/TimerX.git
cd TimerX
git checkout Blur
git fetch && git pull
pip install -r requirements.txt
python main.py

Check the TimerX console on Gitpod for the error. I will test on my RasPi soon, kinda busy.

Uhm, why?

Uhm, why?

To make sure that blur isnt broken on Mac

I was planning to disable it for mac, but ok

And the dmg still doesn't work i thought you guys dropped macos support

It literally did checks for macos

That was just the DMG build. The real test has to be done on a real/imaginary(VM) computer.

But it doesn't run the dmg so i thought you dropped macos support @im-coder-lg

@sumeshir26 can you give me instructions on what to do next in this pr?

@not-nef First, I'll create a PR in the Sun Valley TTk Theme Repo to make the Button and AccentButton background transparent.
Meanwhile, you can figure out how to make acrylic work properly on both light and dark theme.

@sumeshir26 Is there a way to make the corners of the buttons transparent? I think it has to do something with the custom theme because the ttk.Button has no bg parameter

And btw the labels are fixed i just took the old screenshot

@im-coder-lg Can you manually run the checks on this one pls? It still annoys me

Just update your branch and make another change, the checks autoupdate.

Can you check if the file has exactly 702 lines?

Almost the same for me lol.

Did the theme atleast load?

Did the theme atleast load?

Nope.

Can you check if the file has exactly 702 lines?

Yeah it does.

@im-coder-lg Run gh pr checkout 46

That is what I ran, git pulled with --force and ran the main python file. Wait, it could be missing modules, right?

No, run it again. GH CLI creates a local branch if the PR is from another fork, so git pull wont do anything. Also, try to install the requirements again.

Nothing changed. Is there a module error?

Before you ask, the branch is fully updated and I haven't added any new changes.

It's all with the theming! I changed the theme and the old UI is back! So, you might've done something(accidentally) to theming!

For me, it works absolutely beautifully. It is nice and acrilic. can you try to replace all instances of GlobalBlur with Win7Blur?

Also, look here:
https://github.com/TimerX-App/TimerX/blob/6fb4d1dfb613cc3990e65882de4abf15c908d01e/main.py#L133-L144
The title's being used twice, so it's failing. Can we fix this in this PR?

Ok

Fixed

Umm... Is that normal?

GlobalBlur seems to work. However, Win7Blur seems a bad way(check the error above). The Toast Notifier was causing the error, the theming works now. But the toast fails.

Or it was just CMD.

Nothing seems to work yet again.

It seems to have fixed itself. It's puzzling to myself.

Ok, So approve this PR

One minute, apologies. I want to test this again, final test run.

Lets go

@not-nef can you restore this branch?

I'm thinking of reverting this merge, making another PR from this branch and fixing this,

No, he fixed it in #65