Check-in [b9d2ac8f53]

Login
Home Timeline Branches Tags Help

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

Overview
Comment:Editorial fix
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk | minor change
Files: files | file ages | folders
SHA3-256: b9d2ac8f53e66015ffa38d92632725f33b9186f96f86b9b81937ff865996e689
User & Date: dkf 2018-09-15 11:13:19.629
Context
2018-09-15
11:33
Editorial fix check-in: 112d3b968b user: dkf tags: minor change, trunk
11:13
Editorial fix check-in: b9d2ac8f53 user: dkf tags: minor change, trunk
09:26
TIP 430 Final; JN merged implementation check-in: 8fe8b2f057 user: dkf tags: trunk
Changes
Unified Diff Ignore Whitespace Patch
Changes to tip/394.md.
︙︙
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64


 * A scroll-ball rather than a scroll wheel \(see Apple's "mightymouse"\)

 * Additional "forward" and "backward" buttons

 * even more buttons...

On Linux platform, bind'ing on <Button> will catch all\(?\) or these \(and "%b"
gives an ordinal number which allows for some heuristic recognition\). But even
on Linux, it is not possible to bind specifically to e.g. <Button-8>, or to
<B8-Motion> kind of events.

On Windows platform, the system offers different types of events for certain
different controls. An app would e.g. register extra to receive horizontal
scroll events and those extra buttons. \(This is gathered from hearsay.\)

# Proposal

Just like the MouseWheel event that was added to Tk in response to wheel-mice
filling the market, we'd have to define new events for each new control.

For legacy-reasons, the dichotomy between vertical scroll wheel and buttons 4
and 5 will need to be preserved, maybe as well as the buttons 6 and 7 for
horizontal scrolling.

Any extra buttons could then be either named "X1", "X2", "X3", ...  or
numbered 8, 9, 10, ...  which would reflect as bind events <Button-8> or
<Button-X1>, but also <B8-Motion> or <BX1-Motion>

For horizontal scrolling, <MouseWheelHoriz> would be the preferred way for
cross-platform apps, but depending on whether "4 and 5" button events are
already emulated for scrolling on windows, it would be worthwhile to also
emulate "6 and 7" button events for horizontal wheel-activity.

At this stage of this TIP the decision isn't yet made.

# Copyright

This document has been placed in the public domain.









|

|
|















|
|

|











25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64


 * A scroll-ball rather than a scroll wheel \(see Apple's "mightymouse"\)

 * Additional "forward" and "backward" buttons

 * even more buttons...

On Linux platform, bind'ing on `<Button>` will catch all\(?\) or these \(and "%b"
gives an ordinal number which allows for some heuristic recognition\). But even
on Linux, it is not possible to bind specifically to e.g. `<Button-8>`, or to
`<B8-Motion>` kind of events.

On Windows platform, the system offers different types of events for certain
different controls. An app would e.g. register extra to receive horizontal
scroll events and those extra buttons. \(This is gathered from hearsay.\)

# Proposal

Just like the MouseWheel event that was added to Tk in response to wheel-mice
filling the market, we'd have to define new events for each new control.

For legacy-reasons, the dichotomy between vertical scroll wheel and buttons 4
and 5 will need to be preserved, maybe as well as the buttons 6 and 7 for
horizontal scrolling.

Any extra buttons could then be either named "X1", "X2", "X3", ...  or
numbered 8, 9, 10, ...  which would reflect as bind events `<Button-8>` or
`<Button-X1>`, but also `<B8-Motion>` or `<BX1-Motion>`.

For horizontal scrolling, `<MouseWheelHoriz>` would be the preferred way for
cross-platform apps, but depending on whether "4 and 5" button events are
already emulated for scrolling on windows, it would be worthwhile to also
emulate "6 and 7" button events for horizontal wheel-activity.

At this stage of this TIP the decision isn't yet made.

# Copyright

This document has been placed in the public domain.