Late reply but IIRC you must implement OM_SET. I would not use MUI notifications for this kind of events because due to BOOPSI latency... Ilkka
--- On Thu, 24/2/11, Stefan Kleinheinrich <[email protected]> wrote: From: Stefan Kleinheinrich <[email protected]> Subject: [MUI] How to trigger a notify To: [email protected] Date: Thursday, 24 February, 2011, 19:55 Hello, Seems I'm hitting a hard wall here: >DoMethod(timerobj,MUIM_Notify,MA_Timer_Seconds,MUIV_EveryTime,obj,2,MM_Clock_Seconds,MUIV_TriggerValue); This should call MM_Clock_Seconds everytime MA_Timer_Seconds changes. > WaitIO(data->req); > CurrentTime(&raw,µs); > today = raw%86400; > SetAttrs(obj,MA_Timer_Seconds,today%60,TAG_DONE); Shouldn't this one trigger the Notify ? > data->seconds = today%60+30; > data->minutes = (today%3600)/60; > data->hours = today/3600; > data->req->tr_node.io_Command = TR_ADDREQUEST; > data->req->tr_time.tv_secs = 1; > data->req->tr_time.tv_micro = 0; > SendIO((struct IORequest *)data->req); timerobj's OM_GET: > case MA_Timer_Seconds: > *msg->opg_Storage = data->seconds; > return TRUE; Class has no OM_SET. The timer does work (tested by getting MA_Timer_Seconds in every MUIM_Draw for the clock class, but MM_Clock_Seconds never gets called ....
