Ok, that's what I guessed...
so, should we make it use the start of the session as time reference, or
make sure the value is positive, or whatever technique to avoid it from
not working.. or if Arieh's solution works and is tested, then I don't see
why we shouldn't keep it.. why change code
> is because it can return a negative value... maybe check that..
> anyways, Arieh, what is that modulo you put there? since the [clock
> clicks] has nothing to do with the current time, so I guess it can't be
> remove the +10years values.. would it be that the modulo returns always a
> positive nu
great! and great approach Arieh.
I also don't think that it's a threat to have the start time of amsn,
since anyways, with the official client, we'll have the uptime of the pc...
we could have used the start time (t=0) as the time where the webcam
session started, so first frame always has 0,
It's ok :)So the modifications are :- line 849 and line 1535 :set timestamp [ expr { [clock clicks -milliseconds] % 31536 } ]append data "[binary format i $timestamp]"
Yes, I will test it as soon as possible (in few hours i think) and give you a feedback (but this should work).
Very good approach Arieh, thanx a lot. :) I didn't think of the
$::time_now as a big threat, anyway there won't be another way to access
this outside aMSN apart from the webcam headers (and people who haven't
seen the source code still won't know what it means). However, you are
right about da
That is a good solution however there are 2 very minor problems with it.
First is that people will be able to tell from that how long you have had
amsn running for, not sure if that is a good or bad thing, but for privacy
reasons maybe it is bad. Second if somebody changes the date on their
compute
it's ok ;)and you have to modify the line 1535 of msncam.tcl too, with this : set timestamp [ expr { [clock clicks -milliseconds] - $::time_now } ] append header "[binary format i $timestamp]"
2006/5/2, Vivia Nikolaidou <[EMAIL PROTECTED]>:
reggaemanu : thanx from me t
reggaemanu : thanx from me too :)) I came up with an easy approach:
on startup of amsn: for example, file amsn line 59, add this:
set time_now [clock clicks -milliseconds]
when we set the headers: (replacing line 849)
set timestamp [ expr { [clock clicks -milliseconds] - $::time_now } ]
ap
alright, I know what the problem is, and that's what I thought...
the timestamp is a 'windows' GetTickCount timestamp type, which means it's
the number of ticks (milliseconds) since the OS was started. In our case,
I just put in the number of ms since 1970 (the epoch time)... you see,
that m
Hi,So, Youness, we talked about that yesterday, the problem is the timestamp.And there is a problem with the pause function, here is the bugreport :integer value too large to represent while executing
"binary format i [clock clicks -milliseconds]" ("PAUSED" arm line 21) invoked from within
You can confirm what you said by using the Configure Webcam?
Le 05-11-29 à 17:30, Karel Demeyer a écrit :
My ports are configured but still no webcam connection possible ..
aMSN
to MSN 7.0 (latest cvs)
Karel
---
This SF.net email is s
My ports are configured but still no webcam connection possible .. aMSN
to MSN 7.0 (latest cvs)
Karel
[23:26:40] Catch in proc trans (title ): can't read "lang(title)": no such
variable
[23:26:40] Catch in proc trans (followtext ): can't read "lang(followtext)": no
such variable
[23:26:40] Cat
13 matches
Mail list logo
