Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!leah!rsb584 From: rsb584@leah.Albany.Edu (Raymond S Brand) Newsgroups: comp.sys.amiga.tech Subject: Re: Amigix (Re: alarm() function) Summary: consider time fields opaque Message-ID: <1709@leah.Albany.Edu> Date: 24 Mar 89 23:44:58 GMT References: <70@snll-arpagw.UUCP> Organization: his computer Lines: 23 In article , deven@rpi.edu (Deven Corzine) writes: > True. I suppose you could look at the IOrequest which probably > contains the remaining time, but that's not legal, and not nice at > all. So, the question is, is there a legal way to find the time > remaining on a timer request? AbortIO/WaitIO and THEN check the time > fields? Something else? (Preferably something that won't break in > the future...) > > Deven Once you submit a timer request to the timer.device, the time fields of the request are "owned" by the timer.device and are not guarenteed to contain any- thing useful. In fact, the 1.1 and 1.3 autodocs specify that the tr_time field will contain junk when TR_ADDREQUEST returns the message. Fixing-up the time field on an AbortIO could probably be done but that sounds like an enhancement request :-) ------------------------------------------------------------------------- Raymond S. Brand rsbx@beowulf.uucp 3A Pinehurst Ave. rsb584@leah.albany.edu Albany NY 12203 FidoNet 1:7729/255 (518-489-8968) (518)-482-8798 BBS: (518)-489-8968