Issue 68118 - IDL docs for XMouseClickHandler don't explain boolean return values
Summary: IDL docs for XMouseClickHandler don't explain boolean return values
Status: CLOSED FIXED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-03 15:40 UTC by mux2005
Modified: 2017-05-20 09:31 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description mux2005 2006-08-03 15:40:48 UTC
The IDL docs for XMouseClickHandler don't explain what the boolean return values
for mousePressed() and mouseReleased() do.

The docs for XUserInputInterception talk about consuming events, so I guess
that's what these return values are about, but I see no indication as to whether
true means "consume the event" or "pass on the event". The IDL for both
interfaces should be improved.

Interestingly, I've tried to find out what means what by registering 2 handlers
and returning either false or true from both after printing a message. I always
see both messages, so consuming the event (mouseReleased in my testcase) doesn't
seem to work. Is this feature implemented at all?
Comment 1 mux2005 2007-03-16 11:19:19 UTC
Could someone please confirm this issue.
Comment 2 Uwe Fischer 2007-03-16 16:15:29 UTC
change component to 'api'
Comment 3 Uwe Fischer 2007-03-16 16:16:40 UTC
reassigned to owner of component
Comment 4 jsc 2007-03-21 17:01:36 UTC
jsc -> cd: one for the awt owner 
Comment 5 carsten.driesner 2007-03-23 09:53:30 UTC
cd: Accepted.
Comment 6 carsten.driesner 2007-03-27 11:24:13 UTC
cd: Accepted.
Comment 7 Martin Hollmichel 2007-11-09 17:28:03 UTC
set target from 2.x to 3.x according to
http://wiki.services.openoffice.org/wiki/Target_3x
Comment 8 hanya 2014-01-13 15:22:00 UTC
Return values are documented on recent version 4.0.