path: root/src/platformsupport/fontdatabases
diff options
authorGatis Paeglis <>2013-08-07 13:46:21 +0200
committerThe Qt Project <>2013-09-19 12:57:06 +0200
commit663c5186e88e86983532b8010688b38221faab72 (patch)
tree15720f19acbd7efb3b9bfe6f9ec901bf218ec34b /src/platformsupport/fontdatabases
parentbc6f5b3ff61f4b1dea14084349702f2895feda66 (diff)
Fix timing issue in incremental data retrieval mechanism
Make sure that we are not reading wrong PropertyNotify events. From icccm: Requestors may receive a property of type INCR in response to any target that results in selection data. This indicates that the owner will send the actual data incrementally. The selection requestor: - Waits for the SelectionNotify event. - Loops: + Retrieving data using GetProperty with the delete argument True. + Waiting for a PropertyNotify with the state argument NewValue. - Waits until the property named by the PropertyNotify event is zero-length. - Deletes the zero-length property. The issue with the current approach was that after receiving INCR we simply fetched the first PropertyNotify event from the queue, where timestamp indicates that it was generated before INCR, which is not what need. We need PropertyNotify events with a timestamp older than the one on INCR. Task-number: QTBUG-32045 Change-Id: I3b9a006f7d346f67c51e1a296d67a9dc89efadb1 Reviewed-by: Lars Knoll <>
Diffstat (limited to 'src/platformsupport/fontdatabases')
0 files changed, 0 insertions, 0 deletions