Ticket UUID: | 261ec7816cf7c18245fa86b127d9c9a4f193c304 | |||
Title: | Word "catched" on the man page DropSite.html | |||
Type: | RFE | Version: | ||
Submitter: | lindblad | Created on: | 2025-06-24 16:54:47 | |
Subsystem: | (unused) | Assigned To: | nobody | |
Priority: | 5 Medium | Severity: | Minor | |
Status: | Closed | Last Modified: | 2025-07-08 15:09:03 | |
Resolution: | Fixed | Closed By: | aku | |
Closed on: | 2025-07-08 15:09:03 | |||
Description: |
cf: the word catch with its double meaning in Tcl If the “bind” command were that used to capture then this rewording may resolve the confusion. sed -i "s/catched/bound/g" bwidget/BWman/DropSite.html | |||
User Comments: |
aku added on 2025-07-08 15:08:51:
Fixed with commit [3e295548ac]. Changed `catched` to `caught and handled internally`. lindblad added on 2025-06-29 20:19:34: -dropovercmd To me recognise/recognize infers the 3 events are to be made available to the programmer and/or user. However I still wonder if an action is inferred in the code being documented, that is regarding catch or bind. My apologies on the following. cf: https://core.tcl-lang.org/bwidget/tktview/c105497501 sed -i "s/dialogs/dialogues/g" bwidget/ChangeLog sed -i "s/dialogs/dialogues/g" bwidget/utils.tcl According to this ChangeLog entry of 2000-02-18 the foregoing two changes should be reverted. $ sed -n '2313,2314p' bwidget/ChangeLog * color.tcl: Change env(BWIDGET_LIBRARY) to ::BWIDGET::LIBRARY; changed proc "dialogue" to "dialog" $ lindblad added on 2025-06-24 20:35:36: Here's a concrete use in a code comment of the word bound. Though the present tense bind might be the proper grammar in this specific context. $ sed -n '254,257p' utils.tcl # If the window is not mapped, it may have any current size. # Then use required size, but bound it to the screen width. # This is mostly inexact, because any toolbars will still be removed # which may reduce size. $ lindblad added on 2025-06-24 20:19:18: > Perhaps the word recognized or recognised may be used. Noted, however is the below of any use in considering documentation improvement? I presume there is some association of the .html file with the dropsite.tcl file. As follows is the grep output for the -dropovercmd events being documented. $ grep Enter *.tcl arrow.tcl: bind BwArrowButtonC <Enter> {ArrowButton::_enter %W} button.tcl: bind BwButton <Enter> {Button::_enter %W} color.tcl: bind $f <Enter> {focus %W} color.tcl: bind $f <Enter> {focus %W} combobox.tcl: $listb bindText <Enter> [list $listb selection set] combobox.tcl: $listb bindImage <Enter> [list $listb selection set] dialog.tcl: bind $path <KP_Enter> [list ButtonBox::invoke $path.bbox default] dynhelp.tcl: bind BwHelpBalloon <Enter> {DynamicHelp::_motion_balloon enter %W %X %Y} dynhelp.tcl: bind BwHelpVariable <Enter> {DynamicHelp::_motion_info %W} dynhelp.tcl: $path bind BwHelpBalloon <Enter> \ dynhelp.tcl: $path tag bind $tagOrItem <Enter> \ dynhelp.tcl: $path bind BwHelpVariable <Enter> \ dynhelp.tcl: $path tag bind $tagOrItem <Enter> \ notebook.tcl: $path.c bind p:$page <Enter> \ notebook.tcl: $path.c bind $page:jmg <Enter> \ $ grep Leave *.tcl arrow.tcl: bind BwArrowButtonC <Leave> {ArrowButton::_leave %W} button.tcl: bind BwButton <Leave> {Button::_leave %W} dynhelp.tcl: bind BwHelpBalloon <Leave> {DynamicHelp::_motion_balloon leave %W %X %Y} dynhelp.tcl: bind BwHelpVariable <Leave> {DynamicHelp::_leave_info %W} dynhelp.tcl: $path bind BwHelpBalloon <Leave> \ dynhelp.tcl: $path tag bind $tagOrItem <Leave> \ dynhelp.tcl: $path bind BwHelpVariable <Leave> \ dynhelp.tcl: $path tag bind $tagOrItem <Leave> \ dynhelp.tcl:# Leave event may be called twice (in case of pointer grab) notebook.tcl: # the <Leave> event fires and resets data($page,rimage) before notebook.tcl: $path.c bind p:$page <Leave> \ notebook.tcl: $path.c bind $page:jmg <Leave> \ $ grep Motion *.tcl color.tcl: bind $c1 <B1-Motion> [list SelectColor::_select_hue_sat %x %y] color.tcl: bind $c2 <B1-Motion> [list SelectColor::_select_value %x %y] combobox.tcl: ::bind ListBoxHotTrack <Motion> { dragsite.tcl: bind BwDrag1 <B1-Motion> {DragSite::_begin_drag motion %W %s %X %Y} dragsite.tcl: bind BwDrag2 <B2-Motion> {DragSite::_begin_drag motion %W %s %X %Y} dragsite.tcl: bind BwDrag3 <B3-Motion> {DragSite::_begin_drag motion %W %s %X %Y} dropsite.tcl: bind $top <B$evt-Motion> {DropSite::_motion %X %Y} dropsite.tcl: bind $top <Motion> {DropSite::_release %X %Y} dropsite.tcl: set script [bind $_top <B$_evt-Motion>] dropsite.tcl: bind $_top <B$_evt-Motion> {} dropsite.tcl: bind $_top <Motion> {} dropsite.tcl: bind $_top <B$_evt-Motion> {DropSite::_motion %X %Y} dropsite.tcl: bind $_top <Motion> {DropSite::_release %X %Y} dropsite.tcl: bind $_top <B$_evt-Motion> {DropSite::_motion %X %Y} dropsite.tcl: bind $_top <Motion> {DropSite::_release %X %Y} dynhelp.tcl: bind BwHelpBalloon <Motion> {DynamicHelp::_motion_balloon motion %W %X %Y} dynhelp.tcl: $path bind BwHelpBalloon <Motion> \ dynhelp.tcl: $path tag bind $tagOrItem <Motion> \ dynhelp.tcl: $path bind BwHelpVariable <Motion> \ dynhelp.tcl: $path tag bind $tagOrItem <Motion> \ panedw.tcl: bind $top <Motion> [list PanedWindow::_move_sash $top $xmin $xmax %X +%%d+$yr] panedw.tcl: bind $top <Motion> [list PanedWindow::_move_sash \ scrollview.tcl: bind BwScrollView <B1-Motion> [list ScrollView::_set_view %W motion %x %y] statusbar.tcl: bind StatusResize <B1-Motion> \ $ oehhar added on 2025-06-24 17:50:35: I am not so happy with the word "bound". For me "bound" should be folled by "to". This is not the case. Perhaps the word recognized or recognised may be used. Sorry, Harald |
