What's the meaning of XSyncAlarmNotify ?

[danny]

Hi ,

Thank you very much for your answer.


>> And why sometimes the xevent->type is not right? (if the event_base = 96 ,
>> then sometimes the xevent->type always be 98 but not 97)
>
>"Sometimes" before "always" sounds pretty confusing to me. :)

Those codes are from gnome-power-manager program, it will judge the xevent->type, and when it works normally, the xevent->type will be equal with event_base + XSyncAlarmNotify(it is defined as 1), but sometimes the program will become abnormal , then after print the value of xevent->type we found that it will be "event_base + 2" but not "event_base + 1" at this situation.

I am sorry for my poor English to make you confuse.


>Thus,
>whenever a triggering condition of a previously registered alarm occurs, the
>interested client will be notified with a XSyncAlarmNotify event.

Does that means that I could registered XSyncAlarm to the X server?  How to do that, could you tell me? I want to let X server notify me when it has been idle for a given time.

And I will also try to find out from the document you mentioned.
Thanks again.

--

 Best Regards,





At 2010-12-04 23:55:56，"Fernando Carrijo" <fcarrijo.lists at gmail.com> wrote:

>Hi Danny,
>
>danny <tornadory at 163.com> wrote:
>
>> Could you explain about the XSyncAlarmNotify? What's function it provides?
>> Which situation could it be sent by X server?
>
>It seems to me XSyncAlarmNotify is an event type, not a request type. And as
>such, it is delivered from server to clients, not the other way around. Thus,
>whenever a triggering condition of a previously registered alarm occurs, the
>interested client will be notified with a XSyncAlarmNotify event.
>
>With respect to your first email: yes, a XSync enabled server keeps info about
>its idle time but, from the top of my head, I don't remember which piece of the
>protocol you can use to query it.
>
>Anyway, the fact is: the implementation of the XSync Extension, both client-
>and server-side, is kind of easy to understand. Reading the code won't be hard,
>after you grasp the main concepts introduced in the specifications. Give them
>a try!
>
>> And why sometimes the xevent->type is not right? (if the event_base = 96 ,
>> then sometimes the xevent->type always be 98 but not 97)
>
>"Sometimes" before "always" sounds pretty confusing to me. :)
>
>I'm not sure about it.
>_______________________________________________
>xorg-devel at lists.x.org: X.Org development
>Archives: http://lists.x.org/archives/xorg-devel
>Info: http://lists.x.org/mailman/listinfo/xorg-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg-devel/attachments/20101206/593505ef/attachment.htm>