Attachment 88636 Details for Bug 69430 – [08/12] Handler.HandleWith::User_Action_Time: use a signed type

[patch] [08/12] Handler.HandleWith::User_Action_Time: use a signed type

0008-Handler.HandleWith-User_Action_Time-use-a-signed-typ.patch (text/plain), 1.26 KB, created by Simon McVittie on 2013-11-04 18:25:26 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Simon McVittie

Created: 2013-11-04 18:25:26 UTC

Size: 1.26 KB

patch

obsolete

>From d5aa9df2d520e0b5c9a809a1f2423ee400596f51 Mon Sep 17 00:00:00 2001
>From: Simon McVittie <simon.mcvittie@collabora.co.uk>
>Date: Mon, 4 Nov 2013 15:48:38 +0000
>Subject: [PATCH 08/12] Handler.HandleWith::User_Action_Time: use a signed type
>
>User_Action_Timestamp is signed, so this should be signed too.
>---
> spec/Client_Handler.xml | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
>diff --git a/spec/Client_Handler.xml b/spec/Client_Handler.xml
>index 46b9aee..aad76b2 100644
>--- a/spec/Client_Handler.xml
>+++ b/spec/Client_Handler.xml
>@@ -252,14 +252,13 @@ im.telepathy.v1.Channel.Interface.MediaSignalling/video/h264=true
>         </tp:docstring>
>       </arg>
> 
>-      <arg name="User_Action_Time" type="t" direction="in">
>+      <arg name="User_Action_Time" type="x" direction="in"
>+        tp:type="User_Action_Timestamp">
>         <tp:docstring>
>           The time at which user action occurred, or 0 if this channel
>           is to be handled for some reason not involving user action.
>           Handlers SHOULD use this for focus-stealing prevention,
>           if applicable.
>-          This property has the same semantic as <tp:type>User_Action_Timestamp</tp:type>
>-          but is unsigned for historical reasons.
>         </tp:docstring>
>       </arg>
> 
>-- 
>1.8.4.2
>

Actions: View | Splinter Review

Attachments on bug 69430: 88629 | 88630 | 88631 | 88632 | 88633 | 88634 | 88635 | 88636 | 88637 | 88638 | 88639 | 88640 | 92141

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.