[prev in list] [next in list] [prev in thread] [next in thread]
List: xwt-dev
Subject: [xwt-dev] Press/Click events (not) cascading
From: Charles Goodwin <charles.goodwin () credit1 ! co ! uk>
Date: 2002-10-28 17:01:15
[Download RAW message or body]
"When the user presses a mouse button, the value true is put to the box
whose visible area the mouse was inside at the time that the user pressed
the button. Note that transparent boxes are considered opaque for purposes
of determining which box the mouse is in.
If the value true cascades through all the traps on that property and gets
put to the box itself, it is passed to any siblings that the box may be
covering up; if there are none, it is passed up to the box's parent. This
allows the Press event to behave as if it travels along the z-axis, moving
from the box "closest to" the user down to (but not including) the root box,
which is "furthest from" the user."
I'm telling y'all now that this doesn't happen.
<box scrollpane_tag="hlistener">
<box id="header" />
<box id="headerlistener" absolute="true" x="0" y="0" />
</box>
Now $header gets filled with (essentially) buttons. If I delete
$headerlistener then you can click the buttons (ie the up/down effects show)
but with $headerlistener there (with no children) like it is above, you
cannot click the buttons in it's sibling $header (ie nothing happens to the
buttons).
Conclusion: the top statement is either A) False or B) Unintuitive. (_Click1
= function() { arguments.cascade( true ); } does nothing.)
[Attachment #3 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>Press/Click events (not) cascading</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>"When the user presses a mouse button, the value true is put to \
the box whose visible area the mouse was inside at the time that the user pressed the \
button. Note that transparent boxes are considered opaque for purposes of determining \
which box the mouse is in.</FONT></P>
<P><FONT SIZE=2>If the value true cascades through all the traps on that property and \
gets put to the box itself, it is passed to any siblings that the box may be covering \
up; if there are none, it is passed up to the box's parent. This allows the Press \
event to behave as if it travels along the z-axis, moving from the box "closest \
to" the user down to (but not including) the root box, which is "furthest \
from" the user."</FONT></P>
<P><FONT SIZE=2>I'm telling y'all now that this doesn't happen.</FONT>
</P>
<P><FONT SIZE=2><box scrollpane_tag="hlistener"></FONT>
<BR><FONT SIZE=2> <box id="header" /></FONT>
<BR><FONT SIZE=2> <box id="headerlistener" \
absolute="true" x="0" y="0" /></FONT> <BR><FONT \
SIZE=2></box></FONT> </P>
<P><FONT SIZE=2>Now $header gets filled with (essentially) buttons. If I delete \
$headerlistener then you can click the buttons (ie the up/down effects show) but with \
$headerlistener there (with no children) like it is above, you cannot click the \
buttons in it's sibling $header (ie nothing happens to the buttons).</FONT></P>
<P><FONT SIZE=2>Conclusion: the top statement is either A) False or B) Unintuitive. \
(_Click1 = function() { arguments.cascade( true ); } does nothing.)</FONT></P>
</BODY>
</HTML>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic