| Summary: | xdnd_version check issue in case ClientMessage: | ||
|---|---|---|---|
| Product: | SDL | Reporter: | Nitz <nitin.j4> |
| Component: | video | Assignee: | Sam Lantinga <slouken> |
| Status: | RESOLVED FIXED | QA Contact: | Sam Lantinga <slouken> |
| Severity: | major | ||
| Priority: | P2 | ||
| Version: | 2.0.3 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Attachments: |
patch
patch |
||
Should the check be added to the other cases? What's the impact of removing that check? I added xdnd_version check to XdndPosition case also under DEBUG_XEVENTS macro. by this we can get the action requested by user. I analysed further and found out that removing xdnd_version check at XdndDrop case is a bad idea because in XConvertSelection API timestamp should be passed if(xdnd_version >= 1) otherwise CurrentTime should be passed So xdnd_version check is important at XdndDrop case I made xdnd_version as a static so that it can store the version in other cases also. Patch is attached. Thanks!!! Created attachment 1860 [details]
patch
A gentle reminder. Thanks!!! A gentle reminder Thanks!!! Fixed, thanks! https://hg.libsdl.org/SDL/rev/104f3bcfbf45 |
Created attachment 1805 [details] patch In X11_DispatchEvent(_THIS) function: case ClientMessage: In that, value of 32 bit data shifted to 24 bits which is assigned to xdnd_version But xdnd_version has no effect on XdndEnter, XdndPosition, XdndDrop, neither of the cases So I think it would be better if we removed the check of xdnd_version