On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
> On 3/16/2015 2:04 PM, Benjamin Tissoires wrote:
> >On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
> >>On 3/16/2015 12:27 PM, Benjamin Tissoires wrote:
> >>>On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
> On 3/16/2015 7:50 AM,
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
On 3/16/2015 2:04 PM, Benjamin Tissoires wrote:
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
On 3/16/2015 12:27 PM, Benjamin Tissoires wrote:
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
On 3/16/2015 7:50 AM, Jiri Kosina wrote:
On 3/16/2015 2:04 PM, Benjamin Tissoires wrote:
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
On 3/16/2015 12:27 PM, Benjamin Tissoires wrote:
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
On 3/16/2015 7:50 AM, Jiri Kosina wrote:
On Thu, 5 Mar 2015, Benjamin Tissoires wrote:
If
On 3/16/2015 2:04 PM, Benjamin Tissoires wrote:
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
On 3/16/2015 12:27 PM, Benjamin Tissoires wrote:
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
On 3/16/2015 7:50 AM, Jiri Kosina wrote:
On Thu, 5 Mar 2015, Benjamin Tissoires wrote:
If
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
> On 3/16/2015 12:27 PM, Benjamin Tissoires wrote:
> >On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
> >>On 3/16/2015 7:50 AM, Jiri Kosina wrote:
> >>>On Thu, 5 Mar 2015, Benjamin Tissoires wrote:
> >>>
> If noone listens to the input
On 3/16/2015 12:27 PM, Benjamin Tissoires wrote:
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
On 3/16/2015 7:50 AM, Jiri Kosina wrote:
On Thu, 5 Mar 2015, Benjamin Tissoires wrote:
If noone listens to the input device when a tool comes in proximity,
the tablet does not send the
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
> On 3/16/2015 7:50 AM, Jiri Kosina wrote:
> > On Thu, 5 Mar 2015, Benjamin Tissoires wrote:
> >
> >> If noone listens to the input device when a tool comes in proximity,
> >> the tablet does not send the in-prox event when a client becomes
On Mon, 16 Mar 2015, Jason Gerecke wrote:
> This update seems to have solved the issue I was having earlier. I do
> still see some weird behavior with the Intuos3 though. For whatever
> reason, if a tool is in prox and no client is connected, the device
> will repeatedly connect and disconnect
On 3/16/2015 7:50 AM, Jiri Kosina wrote:
> On Thu, 5 Mar 2015, Benjamin Tissoires wrote:
>
>> If noone listens to the input device when a tool comes in proximity,
>> the tablet does not send the in-prox event when a client becomes available.
>> That means that no events will be sent until the tool
On Thu, 5 Mar 2015, Benjamin Tissoires wrote:
> If noone listens to the input device when a tool comes in proximity,
> the tablet does not send the in-prox event when a client becomes available.
> That means that no events will be sent until the tool is taken out of
> proximity.
>
> In this
On Thu, 5 Mar 2015, Benjamin Tissoires wrote:
If noone listens to the input device when a tool comes in proximity,
the tablet does not send the in-prox event when a client becomes available.
That means that no events will be sent until the tool is taken out of
proximity.
In this situation,
On 3/16/2015 12:27 PM, Benjamin Tissoires wrote:
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
On 3/16/2015 7:50 AM, Jiri Kosina wrote:
On Thu, 5 Mar 2015, Benjamin Tissoires wrote:
If noone listens to the input device when a tool comes in proximity,
the tablet does not send the
On 3/16/2015 2:04 PM, Benjamin Tissoires wrote:
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
On 3/16/2015 12:27 PM, Benjamin Tissoires wrote:
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
On 3/16/2015 7:50 AM, Jiri Kosina wrote:
On Thu, 5 Mar 2015, Benjamin Tissoires wrote:
If
On 3/16/2015 2:04 PM, Benjamin Tissoires wrote:
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
On 3/16/2015 12:27 PM, Benjamin Tissoires wrote:
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
On 3/16/2015 7:50 AM, Jiri Kosina wrote:
On Thu, 5 Mar 2015, Benjamin Tissoires wrote:
If
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
On 3/16/2015 12:27 PM, Benjamin Tissoires wrote:
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
On 3/16/2015 7:50 AM, Jiri Kosina wrote:
On Thu, 5 Mar 2015, Benjamin Tissoires wrote:
If noone listens to the input device when a tool
On Mar 16 2015 or thereabouts, Jason Gerecke wrote:
On 3/16/2015 7:50 AM, Jiri Kosina wrote:
On Thu, 5 Mar 2015, Benjamin Tissoires wrote:
If noone listens to the input device when a tool comes in proximity,
the tablet does not send the in-prox event when a client becomes available.
On 3/16/2015 7:50 AM, Jiri Kosina wrote:
On Thu, 5 Mar 2015, Benjamin Tissoires wrote:
If noone listens to the input device when a tool comes in proximity,
the tablet does not send the in-prox event when a client becomes available.
That means that no events will be sent until the tool is
On Mon, 16 Mar 2015, Jason Gerecke wrote:
This update seems to have solved the issue I was having earlier. I do
still see some weird behavior with the Intuos3 though. For whatever
reason, if a tool is in prox and no client is connected, the device
will repeatedly connect and disconnect from
If noone listens to the input device when a tool comes in proximity,
the tablet does not send the in-prox event when a client becomes available.
That means that no events will be sent until the tool is taken out of
proximity.
In this situation, ask for the report WACOM_REPORT_INTUOSREAD which
If noone listens to the input device when a tool comes in proximity,
the tablet does not send the in-prox event when a client becomes available.
That means that no events will be sent until the tool is taken out of
proximity.
In this situation, ask for the report WACOM_REPORT_INTUOSREAD which
20 matches
Mail list logo
