Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!snorkelwacker!bloom-beacon!ATHENA.MIT.EDU!swick From: swick@ATHENA.MIT.EDU (Ralph Swick) Newsgroups: comp.windows.x Subject: Re: xclock Message-ID: <9006281614.AA12765@lyre.MIT.EDU> Date: 28 Jun 90 16:14:30 GMT References: Sender: daemon@athena.mit.edu (Mr Background) Organization: DEC/MIT Project Athena Lines: 17 > Has anyone at MIT considered changing xclock to accept another > argument, a time offset? A long time ago when our kernels were a few weeks out of sync wrt the change in the change in Eastern Standard Time to Daylight Savings Time (or vice-versa, I don't remember now), I hacked in a -offset flag, so the answer is "yes". The hack didn't stay. > Is it possible to update xclock to handle a different time zone > without updating Xaw? probably not. The Clock widget should be fixed to use a callback to get the time and the calls to time() and localtim() should be moved out of the widget into xclock.c in this callback. Now that you know how to do it, we'll expect a bug report with the correct fixes from you soon. :-)