Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | * doc/wheelEvent.html: Slightly extended. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
08e0c1c21ff7720360adaf4653887721 |
| User & Date: | csaba 2019-10-22 13:32:20 |
Context
|
2019-10-22
| ||
| 14:32 | * README.txt: Slightly extended. * doc/scrollutil.html: check-in: f6f45df995 user: csaba tags: trunk | |
| 13:32 | * doc/wheelEvent.html: Slightly extended. check-in: 08e0c1c21f user: csaba tags: trunk | |
| 13:31 | * doc/wheelEvent.html: Slightly extended. check-in: b9ca49d501 user: csaba tags: trunk | |
Changes
Changes to modules/scrollutil/doc/wheelEvent.html.
81 82 83 84 85 86 87 88 89 90 91 92 93 94 |
events will trigger a scrolling of that widget container. Each
<code><i>tag</i></code> argument must be <code><b>all</b></code> or the
path name of an existing toplevel widget (including <code>"."</code>).</dd>
<dd class="tm"><b>REMARK 1:</b> The reason for restricting the
<code><i>tag</i></code> arguments to <code><b>all</b></code> and path names
of existing toplevel widgets rather than supporting also tags like
<code>"BwScrollableFrame"</code> (for BWidget ScrollableFrame) or
<code>"Scrolledframe"</code> (for iwidgets::scrolledframe) is that the
mouse wheel events should trigger a scrolling of the widget container under
the pointer not only if the widget under the pointer is the widget
container itself but also if it is a descendant of the latter (remember
that for each window, the path name of its nearest toplevel ancestor and
the tag <code><b>all</b></code> are contained in the window's default list
|
> |
81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 |
events will trigger a scrolling of that widget container. Each
<code><i>tag</i></code> argument must be <code><b>all</b></code> or the
path name of an existing toplevel widget (including <code>"."</code>).</dd>
<dd class="tm"><b>REMARK 1:</b> The reason for restricting the
<code><i>tag</i></code> arguments to <code><b>all</b></code> and path names
of existing toplevel widgets rather than supporting also tags like
<code>"Scrollableframe"</code> (for scrollutil::scrollableframe),
<code>"BwScrollableFrame"</code> (for BWidget ScrollableFrame) or
<code>"Scrolledframe"</code> (for iwidgets::scrolledframe) is that the
mouse wheel events should trigger a scrolling of the widget container under
the pointer not only if the widget under the pointer is the widget
container itself but also if it is a descendant of the latter (remember
that for each window, the path name of its nearest toplevel ancestor and
the tag <code><b>all</b></code> are contained in the window's default list
|