icy wasp
i have this issue where i cant think of way to find what causing the missbehavior, its about the states.increment(line 39) it should do the following
formated - literal
00:[47;30m00[0m:000 - 0.0
command increment
00:[47;30m01[0m:000 - 1.0
command change_target to 0
command increment
[47;30m01[0m:01:000 - 61.0
but for some reason it didnt do that(with more actions involved)
here is my pastebin
https://paste.pythondiscord.com/RYKQ
loud egretBOT
i have this issue where i cant think of way to find what causing the missbehavio...
@icy wasp
Python help channel opened
shell cedar
what output do you get then
icy wasp
what output do you get then
i format the code to be run
juct comment out the missing lib
shell cedar
just paste the output please, I'm not going to run your code here
icy wasp
okay then
icy wasp
just paste the output please, I'm not going to run your code here
its not gonna show much tho
shell cedar
well how is it misbehaving?
icy wasp
hitoya@hitoya-travelmate5730:~$ python ~/Downloads/programs/tools_cripts/clicker/clicker.py
Node - Timing
03 - 00:04:000
00 - 00:01:000
01 - 00:02:000
['dec']
^CTraceback (most recent call last):
File "/home/hitoya/Downloads/programs/tools_cripts/clicker/clicker.py", line 145, in <module>
main()
File "/home/hitoya/Downloads/programs/tools_cripts/clicker/clicker.py", line 143, in main
screen.join()
File "/usr/lib/python3.12/threading.py", line 1147, in join
self._wait_for_tstate_lock()
File "/usr/lib/python3.12/threading.py", line 1167, in _wait_for_tstate_lock
what is the expected behavior then?
icy wasp
well how is it misbehaving?
its just from 00:00:000 to 59:59:999 a sudden
shell cedar
where do you see 59:59:999
icy wasp
it should give 00:00:000 to 59:00:00 instead
shell cedar
I only see 00:04:000, 00:01:000 and 00:02:000, nothing like what you describe
icy wasp
its not gonna show much tho
exactly what i just said
shell cedar
I don't understand. Do you mean that instead of those 3 lines it should print only 00:00:000 and 59:00:00?
icy wasp
the output was actualy cleared before writing next step
icy wasp
I don't understand. Do you mean that instead of those 3 lines it should print on...
it doest tell much but this what i see
the one on middle is the one supposed change
i dont have proper closing currently so i do interrupt
shell cedar
I don't really understand what this script is even supposed to do
it looks like you have two threads here, why?
icy wasp
just look on the line 39
the states.increment
thats the thing i want to know how i messed up
shell cedar
and they access shared structures but without any kind of synchronization
icy wasp
not sure what that supposed to do or mean
shell cedar
well what is that method supposed to do in the first place?
icy wasp
well what is that method supposed to do in the first place?
it will increment the target value
shell cedar
from the looks of it the logic is a tad more complicated than that
icy wasp
so like
minuites:second:millisec
it will point wich of those 3 then increment
but i represent the data as float
icy wasp
from the looks of it the logic is a tad more complicated than that
well its complex because maybe i simply suck at coding or maybe theres no other solution on my first problem
shell cedar
so states.data is a list of seconds?
shell cedar
I thought they were floats
shell cedar
but if the unit of each element is millisecond then you would only need floats for sub-millisecond accuracy
shell cedar
so the increment static method is used to increment the selected time (determined by pointer), and the field (minute, second, millisecond) is determined by target?
I would advise to simplify the logic of ru() until you get the increment logic right
icy wasp
yes
icy wasp
I would advise to simplify the logic of `ru()` until you get the increment logic...
thast just a way for me to test it
I'll build the input logic later
shell cedar
but this way of testing involves random numbers which makes this more difficult – at least set a constant random seed for reproducible results
icy wasp
random increments/decrements
shell cedar
yes
icy wasp
it only Dec or inc ones
shell cedar
it also randomly changes the field to change
so, let's go over the logic of increment
the number of seconds to add or subtract is basically determined by cls.target, yes?
icy wasp
yes
it will tell if it will increment by minutes, seconds or millisecond
I don't have good name for the states. target
forgive me for that one
shell cedar
I just don't understand why the code is so complex. Isn't the only thing you need to do just:
increment = (60, 1, 0.001)[cls.target]
if not inc:
increment = -increment
cls.data[cls.pointer] += increment
or am I missing something?
icy wasp
I just don't understand why the code is so complex. Isn't the only thing you nee...
determine how much to reduce, increase
if not incrementing make the previous value to negative
add the final value to the index of the current data
I hope that helps
shell cedar
yes, isn't my code doing exactly that?
shell cedar
what was your logic there then
icy wasp
what was your logic there then
that's is bit confusing yes even bit have a headache reminding my self how it works
basically it mods the target value to it's base
the base arrangements is
60,60,1000
it will make decrements put it to the previous value and if it's 0 it will give base-1
shell cedar
why is that necessary when you can just increment the target value?
you only need to break down the value into parts for display purposes
icy wasp
why is that necessary when you can just increment the target value?
well if I decrements when on target = 0
everything will be negative
shell cedar
only if the value drops below zero
if the target value is 61 and you decrement, then obviously it will be 1 afterwards
what part of this is unexpected or unwanted?
icy wasp
?
shell cedar
is there a deeper logic here that you haven't explained yet?
icy wasp
I can put a comment on each line....
shell cedar
they're not helpful to me
icy wasp
let me try to explain how the logic works
shell cedar
maybe this is what you meant: if the value is 0:05:40 and target = 0 and you decrement, you want nothing to change?
icy wasp
i dont understand why its not behaving well but what i wanna hapen there is the value will be 59:05:400
shell cedar
please answer my question
icy wasp
the question is bit vague
icy wasp
what "nothing" is talking to?
shell cedar
that the value remains unchanged
icy wasp
what is the expected end result in that case?
assuming the current value is 00:05:400 if the target is 0 and we will decrement the function should turn it into 59:05:400
shell cedar
I see, so it basically rolls over
icy wasp
thats why "mod"
like a clock
if you ever had a quartz clock
the way you set its digital time
tho you only incement there
shell cedar
ok, next question: if the value is 01:40:59 and target=2 and you increment, what is the end result?
icy wasp
01:40:591
shell cedar
my bad, let me try again
icy wasp
0 = minuites
1 = seconds
2 = millisec
shell cedar
so target=1, value is 01:59:000
icy wasp
the literal value will be 120.0 thus the formated will be 02:00:000
the display will only know what the literal value is
honestly my brain is currently heating up
icy wasp
the latter being 59:59.999
if the code works like how i wanted it should go all 0
shell cedar
I only asked about the valid value range
icy wasp
and if its all zero thenyou decrement while at target = 0 it should go 59:59:999
shell cedar
to make sure we're on the same page
icy wasp
range is 0..60*60-0.001
icy wasp
maybe it would be easier to store the individual fields separately?
hmmmm
the source of those timing are from time.time
icy wasp
maybe it would be easier to store the individual fields separately?
that could work actualy
i can just make classmethod that will add new node
hmmmmm
idk
thanks for the time
it really appreciated
loud egretBOT
Python help channel closed for inactivity