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

Bug fix #3

Open
edoxxx opened this issue Oct 22, 2024 · 3 comments
Open

Bug fix #3

edoxxx opened this issue Oct 22, 2024 · 3 comments

Comments

@edoxxx
Copy link

edoxxx commented Oct 22, 2024

Hi @techn0man1ac it's always me.
I found a small error in the code after adding the function to adjust the time.
the variable Msec has inside it every minute converted to ms if I fix the time are still the minutes already elapsed
For example, if it's 10:24 the clock shows 10:20 if I fix the time at 10:30 The clock will start counting from 10:34, so I think once the time is set, the extra minutes that it has already counted should be taken out.

Edoardo

@techn0man1ac
Copy link
Owner

Hello @edoxxx

Do you have any ideas on how to fix this bug?

@edoxxx
Copy link
Author

edoxxx commented Oct 23, 2024

Hi @techn0man1ac , I don't have a PC at the moment, so I can't test it, but I would do that and I should be able to solve two problems on the code.

I've already described the first problem. The second problem is when you go to adjust the time, if you hold too much and you go too far ahead we have to do a lap of 12 hours.

To solve I add this line of code that will have to be.performed only once when entering the IF of time change

MSec = Msec - (Msec ÷3600000)

So we get the hours and we can fix the minutes and the count starts from 0.

@techn0man1ac
Copy link
Owner

techn0man1ac commented Oct 25, 2024

@edoxxx done . Check it out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants