Mailinglist Archive: opensuse-bugs (9018 mails)
| < Previous | Next > |
[Bug 427645] RANDR doesn't inform about newly plugged monitors
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Fri, 19 Sep 2008 12:59:29 -0600 (MDT)
- Message-id: <20080919185929.2B580245391@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=427645
User mhopf@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=427645#c8
--- Comment #8 from Matthias Hopf <mhopf@xxxxxxxxxx> 2008-09-19 12:59:28 MDT
---
It's most likely that even RandR 1.3 won't have this feature. Also, most
hardware isn't capable of creating interrupts on hotplug change. RandR 1.3
might have a less intrusive scanning operator, though.
(In reply to comment #5 from Lubos Lunak)
This is impossible ATM. Sorry.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
User mhopf@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=427645#c8
--- Comment #8 from Matthias Hopf <mhopf@xxxxxxxxxx> 2008-09-19 12:59:28 MDT
---
It's most likely that even RandR 1.3 won't have this feature. Also, most
hardware isn't capable of creating interrupts on hotplug change. RandR 1.3
might have a less intrusive scanning operator, though.
(In reply to comment #5 from Lubos Lunak)
I didn't expect polling of a RANDR function would have any other effect than
making it tell the client about the change, when it fails to do so on its own.
If you tell me how to get RRNotify_OutputChange about a monitor change without
polling, I'll gladly remove the hack.
This is impossible ATM. Sorry.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |