After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 793821 - Fixing atk event parameters
Fixing atk event parameters
Status: RESOLVED FIXED
Product: java-atk-wrapper
Classification: Applications
Component: general
0.33.x
Other Linux
: Normal normal
: ---
Assigned To: java-atk-wrapper maintainer(s)
java-atk-wrapper maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2018-02-25 22:58 UTC by Samuel Thibault
Modified: 2019-05-01 22:28 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
proposed fix (3.32 KB, patch)
2018-02-25 22:58 UTC, Samuel Thibault 		none Details | Review

Description Samuel Thibault 2018-02-25 22:58:51 UTC 
Created attachment 368907 [details] [review]
proposed fix

Hello,

glib signals have a determined number of parameters, giving an extra 0 is not useful, and missing parameters are of course a problem :) The attached patch fixes the existing mismatches. For bounds_changed, the bogus values could be problematic. It happens that orca actually ignores this kind of event, so it will not be bothered. Provide a (even bogus) parameter is however needed for proper marshalling etc. otherwise undefined behavior would happen.

Samuel
Comment 1 Samuel Thibault 2019-05-01 22:28:39 UTC 
Fixed by 664dc376720f852a214b6cf66647ba9d1a1d5de1 ("Fix atk event parameters")