summaryrefslogtreecommitdiff
path: root/confs/osx.sh
diff options
context:
space:
mode:
authorMarcel Hollerbach <mail@marcel-hollerbach.de>2020-04-14 03:26:05 +0200
committerMarcel Hollerbach <mail@marcel-hollerbach.de>2020-04-14 11:56:29 +0200
commit020cea923e4dfa2103fc3c935d736a464f73d646 (patch)
tree31c4cb19a755b7f77d458031d8f39e5d68651086 /confs/osx.sh
parent96288c7683e7f252e9bcb113818b8cda8a23c31a (diff)
ecore_evas_x: add safety check for data in converterdevs/bu5hm4n/work_dnd
since the existance of seleciton manager, the converter callbacks from ecore_x are expecting custom struct pointers. However, enlightenment never updated to use the elm dnd API for client side usages. Which results in the fact that sometimes, when a client sents Notify, and e_dnd is active, that this converter is executed with the wrong data. With this commit the data passed in is ensured to have the correct magic number. The proper solution for this would either be registering the correct converters in enlightenment, or update to elm_drag. However, since the continues cried river over the last 5 days has raised enough hydro power to add these changes. This leaves us with just one question: How was it possible to generate so many messages about a problem that can be solved in a fraction of charaters that have been written? fixes <a-issue-that-was-never-created> Differential Revision: https://phab.enlightenment.org/D11701
Diffstat (limited to 'confs/osx.sh')
0 files changed, 0 insertions, 0 deletions