Re: Interactive white boards and Fedora Xorg setup

2010-12-01 Thread Adam Jackson
On Wed, 2010-12-01 at 15:58 +1100, Rodd Clarkson wrote:

 Also, where do I get the name for the pointer device?

atropine:~% xinput list
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Unicomp  Endura Pro Keyboard  id=9[slave  pointer  (2)]
⎜   ↳ Macintosh mouse button emulation  id=11   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Power Button  id=7[slave  keyboard (3)]
↳ Unicomp  Endura Pro Keyboard  id=8[slave  keyboard (3)]
↳ Vendor strings are placed here.   Nuforce   µDAC  id=10   [slave  
keyboard (3)]

- ajax


signature.asc
Description: This is a digitally signed message part
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Interactive white boards and Fedora Xorg setup

2010-12-01 Thread Kevin DeKorte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/01/2010 08:09 AM, Adam Jackson wrote:
 On Wed, 2010-12-01 at 15:58 +1100, Rodd Clarkson wrote:
 
 Also, where do I get the name for the pointer device?
 
 atropine:~% xinput list
 ⎡ Virtual core pointerid=2[master pointer  (3)]
 ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
  (2)]
 ⎜   ↳ Unicomp  Endura Pro Keyboardid=9[slave  pointer 
  (2)]
 ⎜   ↳ Macintosh mouse button emulationid=11   [slave  pointer 
  (2)]
 ⎣ Virtual core keyboard   id=3[master keyboard (2)]
 ↳ Virtual core XTEST keyboard id=5[slave  
 keyboard (3)]
 ↳ Power Buttonid=6[slave  
 keyboard (3)]
 ↳ Power Buttonid=7[slave  
 keyboard (3)]
 ↳ Unicomp  Endura Pro Keyboardid=8[slave  
 keyboard (3)]
 ↳ Vendor strings are placed here.   Nuforce   µDACid=10   [slave  
 keyboard (3)]
 
 - ajax
 

Ajax,

I tried this with two mice on my system and I could not seem to restrict
the movement of one of the mice. The properties appear to be set correctly

xinput list-props  Logitech USB-PS/2 Optical Mouse
Device 'Logitech USB-PS/2 Optical Mouse':
Device Enabled (140):   1
Coordinate Transformation Matrix (142): 0.58, 0.00, 0.42,
0.00, 1.00, 0.00, 0.00, 0.00, 1.00

But the mouse still has full run of the screen.

Is there another command I need to run to make the xserver use those values?

Kevin
- -- 
Get my public GnuPG key from
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x7D0BD5D1
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkz2Z/IACgkQ6w2kMH0L1dE7ugCePDOEpMUCFdXtidsBml5DtIDo
afYAn0MZdYEHE3xA6nqiQBBu6/KvBqJo
=QUVL
-END PGP SIGNATURE-
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Interactive white boards and Fedora Xorg setup

2010-12-01 Thread Kevin DeKorte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/01/2010 08:09 AM, Adam Jackson wrote:
 On Wed, 2010-12-01 at 15:58 +1100, Rodd Clarkson wrote:
 
 Also, where do I get the name for the pointer device?
 
 atropine:~% xinput list
 ⎡ Virtual core pointerid=2[master pointer  (3)]
 ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
  (2)]
 ⎜   ↳ Unicomp  Endura Pro Keyboardid=9[slave  pointer 
  (2)]
 ⎜   ↳ Macintosh mouse button emulationid=11   [slave  pointer 
  (2)]
 ⎣ Virtual core keyboard   id=3[master keyboard (2)]
 ↳ Virtual core XTEST keyboard id=5[slave  
 keyboard (3)]
 ↳ Power Buttonid=6[slave  
 keyboard (3)]
 ↳ Power Buttonid=7[slave  
 keyboard (3)]
 ↳ Unicomp  Endura Pro Keyboardid=8[slave  
 keyboard (3)]
 ↳ Vendor strings are placed here.   Nuforce   µDACid=10   [slave  
 keyboard (3)]
 
 - ajax
 

But the properties do seem to work ok with my tablet.

xinput set-prop Wacom BambooFun 4x5 stylus Coordinate Transformation
Matrix 0.43 0 0.57 0 1 0 0 0 1

xinput set-prop Wacom BambooFun 4x5 eraser Coordinate Transformation
Matrix 0.43 0 0.57 0 1 0 0 0 1

Dual head, left is 1680, right is 1280, and I've confined it to the right.

Does the input restraining only work with absolute coordinate devices?

Kevin
- -- 
Get my public GnuPG key from
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x7D0BD5D1
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkz2bNQACgkQ6w2kMH0L1dG3fgCbBIDdFrcZtAu2JBaQLAYH0mX1
WZsAn1/luUBvFT0Pw2PfR9OluVpF97Ha
=cB9G
-END PGP SIGNATURE-
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Interactive white boards and Fedora Xorg setup

2010-11-30 Thread Rodd Clarkson
On Wed, 2010-07-07 at 11:01 +1000, Peter Hutterer wrote:
 [faked-up reply, I'm not on the list, ajax pointed it out to me on the
 archives. please make sure you CC me for any replies]
 
  Unlike a mouse, these pointer devices move the mouse pointer to where
  you touch the screen.  For example, if the IWB is to the right of my
  laptop screen and I touch the right edge of the screen then the mouse
  pointer appears on the right side of my laptop screen, and not where
  I've touched the screen.
  
  The pointer device included with the IWB needs to be able to be
  configured to do two things:
 
  1.  Only work as a device for the IWB screen.  The mouse shouldn't be
  able to be moved off the screen, only around it.
  2.  Calibrate the pointer so that you can declare the
  top/bottom/left/right of the screen (as where the image falls on the
  pointer device isn't usually at the extremes of the device.)
 
  Is this possible?
 
 The 1.9 X server that's already in rawhide has an coordinate transformation
 matrix to restrict absolute devices to essentially any rectangle on the
 screen. The matrix is a property on each device and can be modified with the
 xinput commandline tool (no GUI tools yet).
 
 For example, I've got a 1440x900 and a 1920x1200 display. To restrict my
 tablet to the right (larger) screen:
 $ xinput --set-prop Wacom Intuos4 6x9 Coordinate Transformation Matrix
 0.58 0 0.42 0 1 0 0 0 1  
 
 The matrix thus looks like this:
 | 0.58 0 0.42 |
 | 01 0|
 | 00 1|
 
 giving us a scale into 58% of the screen range with an offset of 42%. Your
 numbers will likely vary but that should fix the issue for you.

Peter,

I've finally found a chance to take a look at this (now that I've got
f14 running on my laptop) and I need a little help understanding the
matrix.

In your case you have two screens with the same aspect ratio (16:10), so
I can see you your right hand screen is 0.58 of the total width and 0.42
across from the left hand side of the span.

However, I've got a situation where one of my screens (on my laptop) is
16:9 (1920x1080) and the other is 5:4 (1280x1024) and I'm not sure how
to set up the matrix for this.  Are you able to supply some extra
'clues'?  Can we assume the laptop screen will be on the left hand side
(as this is how it defaults in Fedora, and I should be able to figure
out how to adjust it if it's not)?

Also, where do I get the name for the pointer device?

I'm sorry to ask, but I've done some searching on google and couldn't
come up with the answers.

regards


Rodd



-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test


Re: Interactive white boards and Fedora Xorg setup

2010-07-06 Thread Rodd Clarkson
On Wed, 2010-07-07 at 11:01 +1000, Peter Hutterer wrote:
 [faked-up reply, I'm not on the list, ajax pointed it out to me on the
 archives. please make sure you CC me for any replies]

Thanks for the reply, and it's nice to know that ajax noticed this (as
it appears ajax has much to do with Xorg on fedora (and I'm guessing
elsewhere)).

  Unlike a mouse, these pointer devices move the mouse pointer to where
  you touch the screen.  For example, if the IWB is to the right of my
  laptop screen and I touch the right edge of the screen then the mouse
  pointer appears on the right side of my laptop screen, and not where
  I've touched the screen.
  
  The pointer device included with the IWB needs to be able to be
  configured to do two things:
 
  1.  Only work as a device for the IWB screen.  The mouse shouldn't be
  able to be moved off the screen, only around it.
  2.  Calibrate the pointer so that you can declare the
  top/bottom/left/right of the screen (as where the image falls on the
  pointer device isn't usually at the extremes of the device.)
 
  Is this possible?
 
 The 1.9 X server that's already in rawhide has an coordinate transformation
 matrix to restrict absolute devices to essentially any rectangle on the
 screen. The matrix is a property on each device and can be modified with the
 xinput commandline tool (no GUI tools yet).
 
 For example, I've got a 1440x900 and a 1920x1200 display. To restrict my
 tablet to the right (larger) screen:
 $ xinput --set-prop Wacom Intuos4 6x9 Coordinate Transformation Matrix
 0.58 0 0.42 0 1 0 0 0 1  
 
 The matrix thus looks like this:
 | 0.58 0 0.42 |
 | 01 0|
 | 00 1|
 
 giving us a scale into 58% of the screen range with an offset of 42%. Your
 numbers will likely vary but that should fix the issue for you.

This looks like a great start, but I'm guessing it only works in 1.9 at
this stage. Will this also work in 1.8?

Obviously a nice GUI tool for this where you can specify the pointer and
the region visually would be the finishing touches (as this will vary
for me from IWB to IWB and I'm a Relief Teacher that sees a lot of
different IWBs.)   Presumably this would be easy enough to implement in
the Monitor Preferences (System  Preferences  Monitor) by including
options to limit pointer devices to a particular display.

The other bit of the problem is defining the mouse region for the
pointer device.  Unlike your wacom device (and similar devices) where
the top left point of the device is quite easier to assume as the top
left corner of the display, IWBs aren't so simple.

IWBs have the image projected onto the screen which is also the pointer
device, but it's very unlikely that the top left corner of the projected
image is also at the same place as the top left corner of the screen.
Since the mouse pointer moves to where you place you finger on the
screen, it's important that this maps precisely so you can click buttons
and drag items without a level of hit and miss (and incorrectly buttons
pressed).  I've even seen IWBs where the image isn't even square on the
IWB, and I guess this needs to be addressed too.

Any suggestions for this?


Rodd



-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test


Interactive white boards and Fedora Xorg setup

2010-07-03 Thread Rodd Clarkson
Hi,

I regularly use (a variety of) interactive white boards and the single
biggest frustration is getting the pointer device working so it's
actually useable.

Let me give you an example.

I plug and IWB into my laptop and Fedora configures is as an extension
to my desktop.  This is great because I can drag what I want to appear
on the IWB and not have to reveal my entire desktop.

The pointer device in the IWB works and I can use it as a mouse, but
it's rendered unusable because the mouse acts across the entire desktop
(both my laptop screen and the IWB).

Unlike a mouse, these pointer devices move the mouse pointer to where
you touch the screen.  For example, if the IWB is to the right of my
laptop screen and I touch the right edge of the screen then the mouse
pointer appears on the right side of my laptop screen, and not where
I've touched the screen.

The pointer device included with the IWB needs to be able to be
configured to do two things:

1.  Only work as a device for the IWB screen.  The mouse shouldn't be
able to be moved off the screen, only around it.
2.  Calibrate the pointer so that you can declare the
top/bottom/left/right of the screen (as where the image falls on the
pointer device isn't usually at the extremes of the device.)

Is this possible?

Does this make sense?

Is this something that's included in f13 (if it is I can't find it) or
could it be included as a part of f14.  As far as I'm concerned this is
a huge feature as I'm constantly finding IWB pointer devices are useless
unless I mirror (and mirroring reveals my desktop and usually squashes
the icons as the laptop screen has to be sized down and then I have to
move the icons back).


Rodd




-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test


Re: Interactive white boards and Fedora Xorg setup

2010-07-03 Thread Kevin DeKorte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07/03/2010 05:10 AM, Rodd Clarkson wrote:
 Hi,
 
 I regularly use (a variety of) interactive white boards and the single
 biggest frustration is getting the pointer device working so it's
 actually useable.
 
 Let me give you an example.
 
 I plug and IWB into my laptop and Fedora configures is as an extension
 to my desktop.  This is great because I can drag what I want to appear
 on the IWB and not have to reveal my entire desktop.
 
 The pointer device in the IWB works and I can use it as a mouse, but
 it's rendered unusable because the mouse acts across the entire desktop
 (both my laptop screen and the IWB).
 
 Unlike a mouse, these pointer devices move the mouse pointer to where
 you touch the screen.  For example, if the IWB is to the right of my
 laptop screen and I touch the right edge of the screen then the mouse
 pointer appears on the right side of my laptop screen, and not where
 I've touched the screen.
 
 The pointer device included with the IWB needs to be able to be
 configured to do two things:
 
 1.  Only work as a device for the IWB screen.  The mouse shouldn't be
 able to be moved off the screen, only around it.
 2.  Calibrate the pointer so that you can declare the
 top/bottom/left/right of the screen (as where the image falls on the
 pointer device isn't usually at the extremes of the device.)
 
 Is this possible?
 
 Does this make sense?
 
 Is this something that's included in f13 (if it is I can't find it) or
 could it be included as a part of f14.  As far as I'm concerned this is
 a huge feature as I'm constantly finding IWB pointer devices are useless
 unless I mirror (and mirroring reveals my desktop and usually squashes
 the icons as the laptop screen has to be sized down and then I have to
 move the icons back).
 
 
 Rodd

Rodd,

I've seen those white boards before. One option you might try is to
disable the display on the laptop so that the IWB was the primary
display. But I do like the idea of being able to tie a input device to a
display.

I could see this feature being useful in a normal dual monitor setup as
well.. where you have a mouse that moves on both screens, but a tablet
that is bound to only one screen. Using a tablet on a dual screen setup
is tough because the horizontal is really touchy.

Kevin


- -- 
Get my public GnuPG key from
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x7D0BD5D1
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkwvJLoACgkQ6w2kMH0L1dE17ACfVmVzFprv4kz6j3ovVTF0ulWC
VuMAn2YvFD+KGJ19cOgGeiQAozh9W3KW
=psy/
-END PGP SIGNATURE-
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test