 ovenwerks yes to database
 no the buttons... while generally going up to down are not the same. some tablets have buttons for the ring keys it has in middle some new tablets doesn't come with buttons at all. with xwacom I had a script that threw out the alphabet in order for each button and I pressed each button once to figure out what was went where. there might
[00:28] <studiobot>  bw a database of this somewhere but I don't know. :(((
 and no probably for this reason button layouts should be tablet specific
[00:29] <OvenWerks> yummy :P
 so a series of layouts for each tablet yeah I know
 there is a reason why my attempts at this never went beyond that wiki document
[00:31] <OvenWerks> @azbulutlu: I think I will start with the assumption that the user has one tablet. That will cover a lot of people.
 but hey at least you can assume people have 1 wacom tablet plugged in at one time
 sorry to be the bearer of bad news
 errr
 the thing is the hard part isn't having multiple tablets
[00:33] <OvenWerks> Peop;e will need to have each tablet plugged in so they can set up that tablet anyway. then we will save that with the device id.
[00:33] <OvenWerks>  But I have to start somewhere
 oh I see
 well as long as it won't make it harder to add it later
 a lot of people might have 1 default layout
 then a couple of layouts for apps they use a lot
[00:35] <OvenWerks> Basically I will need to keep track of any tablet that has ever been attached. Then use that list for set up
[00:36] <OvenWerks> From what I can see of xsetwacom's output, there are only so many things one can do.
[00:36] <OvenWerks> There are up to 12 buttons
 you set them as they are plugged in I think
[00:36] <OvenWerks> there is a possition
[00:36] <OvenWerks> there is a pressure curve
 you cannot even use xsetwacom if yiur tablet is not plugged ib
 in
 sorry I am typing on phone this is not really helping at all
[00:37] <OvenWerks> that is true, but if I have a data base of devices I can save values to a config file of those.
 so when someone plugs in a wacom that's when you want to bring the default setup and possible overrides per application for that tablet
[00:38] <OvenWerks> The first thing I will put in I think, is size position
 size position?
[00:39] <OvenWerks> yeah, the position the tablet maps to on the screen
[00:39] <OvenWerks> This will default to monitor size
 oh yeah that's another fun thing
[00:39] <OvenWerks> (most of the time it does already so far as I can see)
[00:40] <OvenWerks> I have had people who have not had that happen.
 not always but at first phase you need only a few tjings
 things
 stretch to one screen
 stretch to a secondary screen
 stretch to all screens
[00:41] <OvenWerks> I will start with 4 numbers :)
 one option at least to either stretch to a  subsection of the screen that is proportional to the tablet size or use the a subsection of the tablet that is proprtionak to the screen
[00:42] <OvenWerks> Then I will add the 12 buttons, 1 to 3 and 8 to 16
 ok?
[00:43] <OvenWerks> These are what I have on the GUI so far
 honestly I think that is a good start
[00:43] <OvenWerks> Then I will add pressure and pressure curve
[00:44] <OvenWerks> There is one tab for the pad (include buttons) and one for the pen/sylus
[00:44] <OvenWerks> But it seems it may be easier to just use one screen.
[00:44] <OvenWerks> It was just that they show as two devices.
 Id start with 1 screen
 then split it off
 I want to say pen button shortcuts (including the single click double click and eraser click) should be with buttons
[00:46] <OvenWerks> what I would like to do is have a tablet tab that has device sub-tabs
 not on pen tab because these settings will vary based on application
[00:47] <OvenWerks> HID 256c:006e Pen stylus        	id: 11	type: STYLUS    
[00:47] <OvenWerks> HID 256c:006e Pad pad           	id: 12	type: PAD      
 pen pressure and tablet size proportion will probably be separate settings (especially since many drawing apps etc handle their own pressure sensitivity and even have a secondary layer of complexity of brush specific pressure maps)
[00:47] <OvenWerks> That is the device list for one tablet
 yeah pen and pad
[00:48] <OvenWerks> So I can use the bit in the middle as a common device decriptor
[00:49] <OvenWerks>  and assume pen and pad from that. The only time I need those to be in full form is when they actually get set
 the first part yed but why do you need to list the devices?
 oh.. to save settings yeah
[00:52] <OvenWerks> If I am going to have different settings for each device I need some key to refer to them all
 yep no that is good
 I cannot remember if that indicator is model or model plus device ID
 its 4am here and I need to be up in like 5 hours so I will be off to sleep now.
[00:54] <OvenWerks> So a default for all devices that would fill the values for new devices.
[00:54] <OvenWerks> g'nite
 I'll try to lookup matrix transformations this weekend for the screen resize (they are not needed for swapping between screens but it will be needed for anything else - which actually skip stretching between 2 screens for now because I just realized that is quite complicated. my script assumed both screens had the same size which rarely
[00:57] <studiobot>  happens)
 well not rarely but far from guaranteed
[00:57] <OvenWerks> xrabder give lots of info though
[00:58] <OvenWerks> *xrander
 its more that intelligently mapping to 2 screens... depends on screens positions and their relative proportions
 ok I am not talking about this anymore not until I have a chance to double check my old intuos script. and gnight. and I am still very excited you are doing this btw :))