On 12/10/2014 10:17 AM, Keith Packard wrote:
Aaron Plattner writes:
How is a client expected to deal with outputs going away? XSync() and
wire up an error handler around all of its RandR calls? If so, that
sucks.
Like any client deals with any resource which may disappear. Xlib's
error han
Aaron Plattner writes:
> How is a client expected to deal with outputs going away? XSync() and
> wire up an error handler around all of its RandR calls? If so, that
> sucks.
Like any client deals with any resource which may disappear. Xlib's
error handling is pretty painful, but it can be mad
On 12/10/2014 09:29 AM, Keith Packard wrote:
Daniel Martin writes:
Hmm, the awesome Xlib error handling ...
Keith, what do you think, should I change the patch to keep the outputs?
In case, I have to admin, that I can't manage to do this during this
week.
No, we don't need to work around cl
Daniel Martin writes:
> Hmm, the awesome Xlib error handling ...
>
> Keith, what do you think, should I change the patch to keep the outputs?
> In case, I have to admin, that I can't manage to do this during this
> week.
No, we don't need to work around client bugs like that.
--
keith.pack...@
On Wed, Dec 10, 2014 at 3:03 AM, Daniel Martin wrote:
> On 9 December 2014 at 08:14, Aaron Plattner wrote:
>> On 12/08/2014 01:01 AM, Daniel Martin wrote:
>>>
>>> On 5 December 2014 at 17:45, Keith Packard wrote:
Daniel Martin writes:
> From: Daniel Martin
>
> When r
On 9 December 2014 at 08:14, Aaron Plattner wrote:
> On 12/08/2014 01:01 AM, Daniel Martin wrote:
>>
>> On 5 December 2014 at 17:45, Keith Packard wrote:
>>>
>>> Daniel Martin writes:
>>>
From: Daniel Martin
When receiving a hotplug uevent, check if we have to add or remove
On 12/08/2014 01:01 AM, Daniel Martin wrote:
On 5 December 2014 at 17:45, Keith Packard wrote:
Daniel Martin writes:
From: Daniel Martin
When receiving a hotplug uevent, check if we have to add or remove
outputs and act accordingly.
Signed-off-by: Daniel Martin
---
With this patch we cre
On 5 December 2014 at 17:45, Keith Packard wrote:
> Daniel Martin writes:
>
>> From: Daniel Martin
>>
>> When receiving a hotplug uevent, check if we have to add or remove
>> outputs and act accordingly.
>>
>> Signed-off-by: Daniel Martin
>> ---
>> With this patch we create or destroy outputs a
Daniel Martin writes:
> From: Daniel Martin
>
> When receiving a hotplug uevent, check if we have to add or remove
> outputs and act accordingly.
>
> Signed-off-by: Daniel Martin
> ---
> With this patch we create or destroy outputs as a reaction to uevents.
>
> Due to my limited experience, the
On Fri, Nov 28, 2014 at 11:20:53AM +0100, Daniel Martin wrote:
> From: Daniel Martin
>
> When receiving a hotplug uevent, check if we have to add or remove
> outputs and act accordingly.
>
> Signed-off-by: Daniel Martin
> ---
> With this patch we create or destroy outputs as a reaction to ueven
From: Daniel Martin
When receiving a hotplug uevent, check if we have to add or remove
outputs and act accordingly.
Signed-off-by: Daniel Martin
---
With this patch we create or destroy outputs as a reaction to uevents.
Due to my limited experience, the solution is either total crap, cause
I'm
11 matches
Mail list logo
