On Wednesday 25 April 2012 20:34:40 Kai Hendry wrote:
> On 25 April 2012 20:24, Alex Deucher wrote:
> > If the are locked down kiosks then just configure them how you want
> > them statically and then don't let the user change the configuration.
> > If (B) is the most important then why allow user
On 25 April 2012 21:20, Alex Deucher wrote:
> an xorg.conf with several monitor sections whose identifiers match the
Thanks for the suggestion, though I'm trying to avoid the clunky
xorg.conf changes / API. Prefer the xrandr API, but I'm seeing its
limitations.
Hoping someone will get back to m
On Wed, Apr 25, 2012 at 8:59 AM, Kai Hendry wrote:
> On 25 April 2012 20:49, Alex Deucher wrote:
>> Then perhaps provide instructions to walk them through the process?
>
> Well, atm I tell the to go into debug mode and launch a terminal.
> Which is obviously too difficult for many.
>
>> Is all th
On 25 April 2012 21:08, Simon Farnsworth wrote:
> Unless I'm misunderstanding, you have one connected display - you want to
> configure just that display. XRandR tells you which outputs are connected
> (exposed in the xrandr utility as "connected", "unknown" or "disconnected"),
> so your script ca
On 25 April 2012 20:49, Alex Deucher wrote:
> Then perhaps provide instructions to walk them through the process?
Well, atm I tell the to go into debug mode and launch a terminal.
Which is obviously too difficult for many.
> Is all the hw the same or does it vary from kiosk to kiosk? Maybe you
On Wed, Apr 25, 2012 at 8:34 AM, Kai Hendry wrote:
> On 25 April 2012 20:24, Alex Deucher wrote:
>> If the are locked down kiosks then just configure them how you want
>> them statically and then don't let the user change the configuration.
>> If (B) is the most important then why allow users to
On 25 April 2012 20:24, Alex Deucher wrote:
> If the are locked down kiosks then just configure them how you want
> them statically and then don't let the user change the configuration.
> If (B) is the most important then why allow users to mess with the
> displays at all?
Unfortunately I'm relia
On Wed, Apr 25, 2012 at 8:16 AM, Kai Hendry wrote:
> On 25 April 2012 20:05, Marius Gedminas wrote:
>> Do you find the existing GUI tools for monitor configuration inconvenient?
>
> Yes. In Webconverger's case, we deploy kiosks for use in schools and
> libraries. We need to set them up in advance
On 25 April 2012 20:05, Marius Gedminas wrote:
> Do you find the existing GUI tools for monitor configuration inconvenient?
Yes. In Webconverger's case, we deploy kiosks for use in schools and
libraries. We need to set them up in advance on different sorts of
hardware.
Hardware that could be LVD
On Tue, Apr 24, 2012 at 10:38 PM, Kai Hendry wrote:
> Firstly why CC both xorg@lists.x.org, x...@freedesktop.org ?
I just replied to your email. I didn't change the addresses.
>
> On 25 April 2012 01:02, Alex Deucher wrote:
>> The names give a pretty good indication as they generally map to th
On Wed, Apr 25, 2012 at 10:38:47AM +0800, Kai Hendry wrote:
> Firstly why CC both xorg@lists.x.org, x...@freedesktop.org ?
That's my fault, and I apologize. Mutt noticed the List-Post header
(which was different from the To header) and decided to include both
addresses when I used it's list-reply
Firstly why CC both xorg@lists.x.org, x...@freedesktop.org ?
On 25 April 2012 01:02, Alex Deucher wrote:
> The names give a pretty good indication as they generally map to the
> physical connector.
Understood, but I'm looking for a simple "default", which I have seen
on some setups in the past.
On Tue, Apr 24, 2012 at 12:13 PM, Kai Hendry wrote:
> Thanks, if you don't know if the screen is LVDS1, HDMI1 or VGA1 etc.
> How are people expected to script it? Just grep " connected"?
The names give a pretty good indication as they generally map to the
physical connector.
Alex
___
Thanks, if you don't know if the screen is LVDS1, HDMI1 or VGA1 etc.
How are people expected to script it? Just grep " connected"?
Thanks,
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/m
On Tue, Apr 24, 2012 at 12:40:53PM +0800, Kai Hendry wrote:
> I'm a bit confused by how xrandr seems to accomplish the same things
> in two different ways.
>
> For example:
>
> xrandr --output LVDS1 --mode 1366x768 VERSUS to xrandr -s 1366x768
>
> xrandr --output HDMI1 --rotate left VERSUS xrand
15 matches
Mail list logo
