Bwidget Source Code
Check-in [3e295548ac]
Not logged in
Core Home Timeline Branches Tags Tickets Wiki Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Doc fix. Ticket <261ec7816c>.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | trunk
Files: files | file ages | folders
SHA3-256: 3e295548ac96eb2d287623262ec583f7dc8af5c76017c68d4546244509227bcf
User & Date: aku 2025-07-08 15:07:41.075
References
2025-07-08
15:08 • Ticket [261ec7816c] Word "catched" on the man page DropSite.html status still Open with 3 other changes artifact: 151d7c8b0a user: aku
Context
2025-07-08
15:07
Doc fix. Ticket <261ec7816c>. Leaf check-in: 3e295548ac user: aku tags: trunk
2010-12-14
17:01
* tree.tcl [Bug 3106208]: Followup. Moved the fixed code of the last entry I did (2010-11-09) into a new command Tree::MergeFlag and call this from both Tree::itemconfigure and Tree::insert. Missing the place in Tree::insert caused another problem, found by Dustin Littau. check-in: c3b144fc1f user: andreas_kupries tags: trunk, tcllib-1-13, tcllib-1-14
Changes
Unified Diff Ignore Whitespace Patch
Changes to BWman/DropSite.html.
︙︙
85
86
87
88
89
90
91
92

93
94
95
96
97
98
99


</DD>
</DL>
<DL><DT><A NAME="DropSite-dropovercmd"><B>-dropovercmd</B></A></DT>
<DD>

This command can be used to provide a dynamic drag while <I>drag-over</I> events.
While a drag occurs, events &lt;Enter&gt;, &lt;Motion&gt; and &lt;Leave&gt; are catched.

Arguments passed to the command are:
<UL>
<LI>pathname of the drop target (the widget itself),
<LI>pathname of the drag source,
<LI>event over the drop target: <I>enter</I>, <I>motion</I> or <I>leave</I>,
<LI>root x-coordinate of the pointer,
<LI>root y-coordinate of the pointer,








|
>








85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100


</DD>
</DL>
<DL><DT><A NAME="DropSite-dropovercmd"><B>-dropovercmd</B></A></DT>
<DD>

This command can be used to provide a dynamic drag while <I>drag-over</I> events.
While a drag occurs, the events &lt;Enter&gt;, &lt;Motion&gt; and
&lt;Leave&gt; are caught and handled internally.
Arguments passed to the command are:
<UL>
<LI>pathname of the drop target (the widget itself),
<LI>pathname of the drag source,
<LI>event over the drop target: <I>enter</I>, <I>motion</I> or <I>leave</I>,
<LI>root x-coordinate of the pointer,
<LI>root y-coordinate of the pointer,
︙︙