|
From: Brad L. <bra...@gm...> - 2018-06-25 14:24:29
|
On Mon, Jun 25, 2018 at 6:29 AM, Arjen Markus <Arj...@de...>
wrote:
> Hi everyone,
>
>
>
> Wrt this TIP, I have a first version of an implementation ready, but when
> I examined the bindings, I noticed that there is considerable variation in
> how the “delta” is communicated: on OSX %D gets replaced by -1 or +1, on
> Windows %D gets replaced by -120 or +120. In my implementation for Linux it
> would be -1 and +1 again.
>
>
>
> As the various widgets cope with this variety, I wonder how many packages
> would be affected if I try to make %D behave uniformly. Would it be a
> better idea to introduce a new binding code, like, say, %r (for rotation –
> angle (a, A), and d are already taken)? Its values would be -1 or +1. %D
> could still contain the current platform-dependent value.
>
>
It would affect many packages I am guessing.
I have in one package:
# $d is the %D value
if { $sdvars(os.windows) } {
set d [expr {int(-$d / 120)}]
}
if { $sdvars(os.macosx) } {
set d [expr {int(-$d)}]
}
A new binding code would be better. I could simplify my code.
The ticket: http://core.tcl.tk/tk/info/75d38f8608 has some information on
delta handling on windows.
Bug fixes for high resolution mouse wheels on windows.
How these high resolutions mouse wheels get handled on Linux and Mac OS X
is unknown.
|