it reads the time from whatever windows is set to using the standard time API, so it will use whatever time windows is set to
of course your system is currently set to half of the stuff thinks it's one time and half of it thinks it's a different time, so... expect weird things - btw the problems are well known and not WCS specific, as i mentioned WCS uses standard APIs to get the local time (the localtime() function in fact), any other program doing it using the same function will ave the same problem, although some functions are reporting the correct time for your system others aren't...
be a lot simpler if they just scrapped the stupid clock changes, seriously, if you want it to be lighter when you wake up get up an hour later, and if you want it to be lighter when you go to sleep, go to sleep an hour earlier - why should everyone else have to mess about with their clocks for a handful of people who insist on doing things that depend on daylight using the time displayed on a clock instead of the current daylight?
nylly: that's only on linux, where it uses the current unix time as its timer for everything, on windows it uses the system uptime which is independent of the clock for internal timing, but on linux it's harder to get access to that timer so it uses the current time instead... that's only for internal time keeping though and it uses a different time API for displaying times on things (the time displayed for stuff isn't used anywhere except for displays, current unix time is all it uses internally, which is timezone independent)
