Nux

Timestamp field on the event structure is always 0

Bug #735645 reported by Alejandro Piñeiro
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Nux
Fix Released
Undecided
Jay Taoko
Unity
Fix Released
Undecided
Unassigned
nux (Ubuntu)
Fix Released
Undecided
Unassigned
unity (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Due my work on the bug 702672 I added a event inspector, and one of the data that I need to remit from the atk layer is the timestamp of the event.

Class Event (defined on NuxGraphics/Events.h) includes a e_x11_timestamp. But it is always 0, it is not filled with the proper timestamp.

For my case, I will try to get the time from the system (although localtime reports seconds and I need milliseconds), so the priority is low, but this bug should be solved eventually.

Tags: a11y

Related branches

Changed in nux:
status: New → Confirmed
Changed in unity:
status: New → Confirmed
Alex Launi (alexlauni)
Changed in nux (Ubuntu):
status: New → Confirmed
Revision history for this message
Alejandro Piñeiro (apinheiro) wrote :

After a brief talk with Alex Launi on IRC, and as this is a nux bug, we conclude that Jay is usually a good recipient of nux bugs, so I'm assigning the bug to him.

As I said on the description, note that I was able to workaround this bug (see unity_util_accessible.ccp::atk_key_event_from_nux_event_key) , so it should be a low priority bug.

Anyway it would be good to solve this bug eventually, in order to avoid that call to g_get_real_time on any user keystroke.

Changed in nux:
assignee: nobody → Jay Taoko (jaytaoko)
Revision history for this message
Jay Taoko (jaytaoko) wrote :

Added time stamp on KeyPress and KeyRelease events. I am marking this bug as fixed. The time stamp will be added to other events eventually, but if this is an urgent need, then reopen this bug.

Changed in nux:
status: Confirmed → Fix Committed
Changed in unity:
status: Confirmed → Fix Committed
Changed in nux (Ubuntu):
status: Confirmed → Fix Committed
Changed in unity:
milestone: none → 6.2
Changed in nux:
status: Fix Committed → Fix Released
Changed in unity:
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nux - 3.2.0-0ubuntu1

---------------
nux (3.2.0-0ubuntu1) quantal-proposed; urgency=low

  [ Łukasz 'sil2100' Zemczak ]
  * New upstream release.
    - REGRESSION: can't type characters with accent (dead keys) (LP: #961741)
    - still some accent issues with unity/nux (LP: #950740)
    - nux source bundles tinyxml (LP: #789303)
    - Support for automation (LP: #685199)
    - add alpha function on a NuxBaseWindow (LP: #718827)
    - Timestamp field on the event structure is always 0 (LP: #735645)

  [ Adam Conrad ]
  * Removed debian/patches/02_libgeis_rename.patch

  [ Didier Roche ]
  * debian/control:
    - build-dep on a recent geis
 -- Lukasz 'sil2100' Zemczak <email address hidden> Fri, 10 Aug 2012 11:47:53 +0200

Changed in nux (Ubuntu):
status: Fix Committed → Fix Released
Changed in unity (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.