@@ -93,10 +93,10 @@ <h3 id="ov_what">What Is Scrollutil?</h3>
93
93
< li > reference pages in HTML format.</ li >
94
94
</ ul >
95
95
96
- < p > The scrollutil::scrollarea mega-widget greatly simplifies the creation of
97
- arbitrary scrolled widgets. It consists of a scrollable widget and two
98
- scrollbars connected with that widget. The display mode of each
99
- scrollbar can be < code > static</ code > , < code > dynamic</ code > , or
96
+ < p > < b > The scrollutil::scrollarea mega-widget</ b > greatly simplifies the
97
+ creation of arbitrary scrolled widgets. It consists of a scrollable
98
+ widget and two scrollbars connected with that widget. The display mode
99
+ of each scrollbar can be < code > static</ code > , < code > dynamic</ code > , or
100
100
< code > none</ code > . This scrolled window implementation also supports
101
101
the widgets that are scrollable in one direction only (e.g., entry and
102
102
ttk::entry) and respects the header component and title columns of < a href =
@@ -115,25 +115,26 @@ <h3 id="ov_what">What Is Scrollutil?</h3>
115
115
Tcl 8.5) TclOO. It is also free from the < a href =
116
116
"https://wiki.tcl-lang.org/page/Scroll+bars+that+appear+only+when+needed "> shimmering
117
117
problem in connection with text widgets</ a > , which the above-mentioned
118
- scrolled window implementations either share with the autoscroll package or
119
- circumvent in a suboptimal way.</ p >
120
-
121
- < p > The scrollutil::scrollsync mega-widget is designed for scrolling several
122
- widgets simultaneously. Whenever the horizontal/vertical position of
123
- the view in the window of one of its widgets changes, the view in the windows
124
- of all the other widgets is automatically adjusted accordingly, thus making
125
- sure that the view's position in these windows is kept in sync. This
126
- mega-widget is horizontally and vertically scrollable, hence it can be
127
- embedded into a scrollutil::scrollarea widget.</ p >
128
-
129
- < p > From the point of view of the commands for mouse wheel event handling
130
- provided by the Scrollutil package, the scrollability of a widget container
131
- window means that the associated Tcl command supports the < code > xview
132
- scroll < i > number</ i > units</ code > and < code > yview scroll
133
- < i > number</ i > units</ code > subcommands. The reason for requiring
134
- at least Tk version 8.6b2 on Windows for these commands is that in earlier Tk
135
- versions on this platform the mouse wheel events were sent to the widget
136
- having the focus rather than to the one under the pointer.</ p >
118
+ scrolled window implementations either share with the autoscroll package
119
+ (contained in tklib) or circumvent in a suboptimal way.</ p >
120
+
121
+ < p > < b > The scrollutil::scrollsync mega-widget</ b > is designed for scrolling
122
+ several widgets simultaneously. Whenever the horizontal/vertical
123
+ position of the view in the window of one of its widgets changes, the view in
124
+ the windows of all the other widgets is automatically adjusted accordingly,
125
+ thus making sure that the view's position in these windows is kept in
126
+ sync. This mega-widget is horizontally and vertically scrollable, hence
127
+ it can be embedded into a scrollutil::scrollarea widget.</ p >
128
+
129
+ < p > From the point of view of < b > the commands for mouse wheel event
130
+ handling</ b > provided by the Scrollutil package, the scrollability of a
131
+ widget container window means that the associated Tcl command supports
132
+ the < code > xview scroll < i > number</ i > units</ code > and
133
+ < code > yview scroll < i > number</ i > units</ code > subcommands. The
134
+ reason for requiring at least Tk version 8.6b2 on Windows for these commands
135
+ is that in earlier Tk versions on this platform the mouse wheel events were
136
+ sent to the widget having the focus rather than to the one under the
137
+ pointer.</ p >
137
138
138
139
< p > To make use of the user-friendly mouse wheel event handling via the
139
140
Scrollutil package, follow the steps below:</ p >
0 commit comments