<slightlyoff> jrossi: no, on
the call, but don't want to queue in just to say "not today" =
)

<slightlyoff> why?

<jrossi> just curious

JR: I'll reply to the pointerID
thread

AR: why do people not want to
make it opaque?

JR: I found UCs for it being an
integer

… in one painting demo with multitouch, used
integer to pick from a random number of colors

… perhaps not a great UC

… Do you have a proposal for opaque?

AR: think object identity should
be sufficient

… can't guarnatee integer stability

… having multiple mouse isn't common

… One objection is only having one mouse and
making it 0

… Don't think we want an integer for a
specific device

… Breaks down when new pointer types are
added

… Don't want to set bad expectations

JR: Rick mentioned some issues
with using integers

… e.g. when comparing

… May need to add some more context about the
integers

… Can achieve good level of interop with
integers

… and make sure people's "false assumptions"
are addressed

… Think this would be a problem for our
impl

… if we had to switch to opaque types

… I am willing to consider it, but would
prefer to keep this integer

… and to add some more information and
context

… One pain point is supporting touch events
which used integer

AR: given that, I think it would
be ok if using integers was fleshed out better

… that would be better than creating an
interop problem

JR: do you have a proposal?

AR: opening move is to write down
the IE behavior

… then we have something to discuss

DS: is part of your rationale
pattern searching?

AR: if integers, it permits
indexing to arrays

… and that works ok if the impl moves through
the integer space in a reasonable way

… but if a different impl moves through the
integer space differently, there will be interop problems

… Don't want confusion for the app devs

… if the id is overloaded

DS: so, need to define the
semantics of the integer e.g. before/after

AR: need to make sure impls
handle integers the same way

OP: I prefer a random
behavior

AR: and that would meet my opapue
requirement

<jrossi> Roughly speaking,
IE10 reserves 1 for mouse. Then 2+ values are used for other
inputs. With each newly recognized pointer, the ID is
increased. But there's some max at which we wrap back around to
2. I'd have to check with the Windows kernel folks for
clarity.