On Wed, Jul 27, 2016 at 10:45:10PM -0400, Scott Kostyshak wrote: > > Enrico, have you seen the following? > https://codereview.qt-project.org/#/c/32263/ > > In particular, note the patch set here: > https://codereview.qt-project.org/#/c/32263/7//ALL > > "Clients attempting to acquire a selection must set the time value of > the xcb_set_selection_owner request to the timestamp of the event > triggering the acquisition attempt, not to XCB_CURRENT_TIME." > > Does this mean that setting to XCB_CURRENT_TIME in cb0c881b should be > changed to something else? I don't actually understand. I don't even > know if LyX is the "client" here (I would have guessed that "client" > referred to the application retrieving the selection, not writing it). > > I have no idea if the above is relevant. Even if it is, if you don't > feel like spending more time on this, please don't. It is a minor issue > and you already committed a patch that works, so I doubt it is worth any > more of your time. I just send this to you in case it captures your > curiosity.
Before coming up with that patch I had tried setting the current timestamp but nothing happened (it didn't work). Then I tried setting the timestamp some seconds into the future and weird things occurred: LyX was the only application that could acquire ownership of the primary selection and all other applications were not able to select anything until the time elapsed. Then I used XCB_CURRENT_TIME and it worked flawlessly. I am really no expert in the innards of the X server, I simply see that it works. -- Enrico
