Hi Bastien, I did some experiments back in 2010 for potentially using these tiny displays in blender, but could access them only through the Mac driver, so put the project on the back burner. Will these soon be accessible on Linux as well?
The images are 4-bit grayscale. PNG handles this format perfectly, as long as you have good tools. Overall display dimensions are 64x128 as oriented, with each button's icon being 64x30, and a 2-pixel gap between icons. Examination with a flashlight told me that these "gap" pixels are physically present, but unlit. As far as needing to rotate before sending to the hardware... I don't know, but I'm sure someone else here does! Just a guess: We will probably have to update images at a display granularity (shared by 4 buttons). So a single icon is tied to its 3 neighbors, but not to the 4 icons on the other display. Tonight I'll look into what info is visible from the Mac USB prober, and report back. Hope some of this is helpful. Mike Erwin musician, naturalist, pixel pusher, hacker extraordinaire On Thu, Feb 2, 2012 at 1:54 PM, Bastien Nocera <[email protected]> wrote: > Heya, > > Instead of hitting just Peter with this sort of question[1], I'm > guessing that there are quite a few people on the list that could answer > my questions (or point me to the relevant Wiki pages). > > For the fun that's about to be had with the Intuos4 LEDs, a couple of > questions: > - is there/will there be a way to avoid getting/updating/setting all the > LEDs when changing one? What format do the LEDs graphics needs to be in? > - can wacom provide a library of pixmaps for us to use for the LEDs, so > that they look like they already do on Windows or MacOS X, or would we > have the time consuming task of re-doing them? If the problem is simply > that the data isn't easily available, we can certainly try and nab it > from the other drivers. > - will we need to handle rotation ourselves, and rotate the LED drawings > ourselves? > - what metadata does one need to associate a button with an LED > placement? > - Any ideas what a sane API would look like (eg. if you didn't have to > use device properties, how would you have implemented it? :) > > -How does one grab events from the touchring when used with the stylus? > xev refuses to show anything. > > Cheers > > [1]: Instead I get him to check whether we support all 22 "mouse > buttons" on the Cintiq 21UX2 :) > https://bugs.freedesktop.org/show_bug.cgi?id=45557 > > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > Linuxwacom-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
