Aiptek Hyperpen 8000u Driver
2021年2月11日Download here: http://gg.gg/o9ob5
Aiptek Hyperpen USB tablet drivers for Linux and X.Org/XFree86. Also includes GUI front-end for configuring the tablet while in-use. Supports Aiptek 6000U, 8000U, 12000U. May work with 4000U/5000U, also reported to work with off-brand clones such as LT95.
(interrupt to exit) ^C trak@. Input$ uname -a Linux traktir.trak.spb.ru 2.6.4 #3 Wed Mar 24 13:35:02 MSK 2004 i686 unknown trak@. Input$ /sbin/modinfo aiptek author: Bryan W. Headley/Chris Atenasio description: Aiptek HyperPen USB Tablet Driver (Linux 2.6.x) license: GPL parm: programmableDelay:delay used during tablet programming parm. Downloads 6 Drivers and Manual for Aiptek HyperPen 8000U Other Peripherals. Here’s where you can downloads the newest software for your HyperPen 8000U. We support the following digital tablets: Aiptek HyperPen 4000U, 5000U, 6000U, 8000U, and 12000U. Other tablets we have found to be similar enough include, the Trust Wireless Tablet 400, LIFETEC LT9750, and Medion MD9750. The goal in developing these drivers is to provide a usable working environment for the user and tablet under. Download Aiptek HyperPen Drivers for Windows 10 X64 27.40.358.3338 for free here.
Aiptek, Inc, manufacturesand markets the HyperPen series of USB digital tablets. Aiptek does not,however, offer device drivers for Linux, nor for the X Window System runningon Linux. This project addresses that need by developing Linux and X WindowSystem device drivers. Additionally, we develop an X-based TabletManager, that allows the user to query and dynamicallyreconfigure the device driver’s settings, while the tablet is inactive use.
We support the following digital tablets: Aiptek HyperPen 4000U,5000U, 6000U, 8000U, and 12000U. Other tabletswe have found to be similar enough include, the Trust Wireless Tablet 400, LIFETEC LT9750, and Medion MD9750.
Project Goals
The goal in developing these drivers is to provide a usableworking environment for the user and tablet under Linux. Our goalis to deliver a suite of components that is, first, concernedwith supporting your hardware, second, with supporting yourhardware in the most likely user environment you’ll be using -- the X Window System -- and finally, concernedwith providing you with a usable workflow. These components are,
*TheLinux Kernel device driver delivers tablet movement reportsthrough a device driver interface. Additionally, it offers a text-modeinterface, through the sysfs pseudo-file API (procfsunder Linux 2.4.x) to inspect and dynamically reconfigure the driverand/or your tablet. We support Linux 2.6 and 2.4.
*TheX Window Input Driver reports tablet events to theX Window System, permitting X Window applications to work with thetablet. This driver also supports reporting its status and dynamicreconfiguration; the user interface for doing so is none other than,
*TheTablet Manager presents reports from the Kerneland X Window device drivers in an easy-to-read format for the end user.Settings for both drivers can be inspected and dynamically reconfiguredfrom the Tablet Manager.
The Gaiptek Tablet Manager is a front-end to the programmatic featuresfound in the Linux Kernel Device Driver and the X11 Input Driver. Withthe Tablet Manager, you can inspect and dynamically program the tablet,as well as inspect and modify the behavior of the two drivers. Doing sodoes not mean you have to reboot or reload the driver, nor do you have torestart the X Server.
Having the Gaiptek Tablet Manager running does not affect the normaluse of your tablet: you can have it active while running otherapplications. It won’t affect the tablet or its driver’s behavior until you reprogram them.
Both the Kernel and X Server Drivers support bidirectional interactionwith the user. The X Server Driver uses the Tablet Manager as the front-endto its programmatic interface. The Linux Kernel driver natively supportsa file-oriented user interface, through the sysfs (or procfs on Linux2.4.x) virtual file system. We believe you’ll find the file-orientedinterface useful in batch processing, but will use this interface the majority of the time.
The Tablet Manager is actually three programs in one. One section of theprogram communicates with the Kernel Driver. The other communicates with theX Server Input Driver. The remaining section provides diagnostics for your tablet. Along those lines, we attempted to break down the screens by their function.
Looking at the main screen, you’ll notice that we have set up a tab controlalong the left side of the screen. Those tabs control whether you see Kernel-,X Server-, or Diagnostics-related screens. The left-handed tab controls appearon every page.
But those are not the only controls that appear on every page. The menubar and associated toolbar appears on every page, as well as the series of buttonscalled the ’Stylus Tools’ appears on every page, at the same location.
The controls along the top of the screen are Kernel Driver-related; thebottom controls are Kernel Driver-related, although you’ll mostly see theiraffect through the X Server Driver. The point is, the two drivers are veryinterdependent: someone wanting to configure one driver may well want to alsowork with the other driver.1. Which Tablet Is Being Managed?
The first control is something that’s not very apparent at first –the Window’s title decoration. We use it to convey which tablet you areinspecting and/or programming.
One of the problems we have, when supporting multiple tablets, isconveying which tablet is presently being viewed and/or modifiedto you in an obviousway. The Linux Kernel does not assign device driver entries for USBinput devices in the same way as it does for RS-232C. E.g., there is no/dev/tty01 that always refers to the device connected to the firstserial port. And, should no device be attached to the given serial port,the device entry will still exists in /dev.
Instead, for input devices, the kernel might assign adevice entry like, /dev/input/event5, to your tablet. But even then,that device entry assignment is transitory: it can change everytime you reboot your system. (There is background on this that we’lldiscuss later.)
We get around this issue by displaying the USBconnector that’s physically attached to your tablet. If you lookat thetitle bar shown below, we display that information, much like otherprograms will display the name of the file they are editing.
2. The “Button” Controls
You’ll notice in the above picture, that there are a series ofbuttons going along the top of the page. These buttons appear on allpages of the Tablet Manager.2.1 The “Open Tablet” Button
Knowing what we now know about the Window’s title, and how we addresstelling you which tablet is being presented, you might wonder how to have theTablet Manager deal with your other tablet(s). That’s easy – press the“Open Tablet” button, or choose Tablet|Open Tablet from the menu, and you will see thefollowing panel:
And as you might expect, the pull-down has the list of Aiptektablets controlled by the Linux Kernel Device Driver, identified by theUSB connector they are attached to. Merely choose the correct tablet,and press the “OK” button. The panel disappears, and the Tablet Managerdisplays information about the new tablet.
Now, if you only have one tablet, do you need to go through theprocess of selecting and opening a tablet? No, (and also, No, if youhave more than one) the Tablet Manager will automatically find and openthe first Aiptek tablet it finds.
Of course, if you were in the process of reconfiguring the previoustablet, and did not yet go through the process of reprogramming itfirst, you’ll lose your changes. Which is why there is a “Cancel”button. But it does beg the question, how do you program your tablet?2.2 The “Program” Button
If you are in the process of modifying your tablet’s configuration,or the Linux Kernel Device Driver’s configuration, you might move theTablet Manager from page to page, setting the parameters you wantchanged. And then, when satisfied, you’ll want to program the tablet.This is what the “Program” button, or the Tablet|Program menu option,does for you.
(As you will later see, there is another “Program” Button elsewherein the Tablet Manager, so let us stress: the one along the top of the screen deals with the LinuxKernel Device Driver. Don’t set attributes for the X Server Driver andexpect this button to program them for you. It won’t. It just programs theKernel Driver’s attributes. No harm will come of it ifyou do, but we’d like to avoid frustrating you if we can.)2.3 The ’Refresh’ Button
While inspecting/setting attributes from the Linux Kernel DeviceDriver, you might decide that you want to throw away your changes, andhave the Tablet Manager, instead of showing your pending changes,instead re-present the tablet’s and Linux Kernel Driver’s current state. Howto do this? With the “Refresh” button, or the Tablet|Refresh menu option.
(Again, this refreshes attributes from the Linux Kernel DeviceDriver. Not from the X Server Driver. And yes, there is another“Refresh” button, but it only appears on the X Server page. We’lldiscuss that later.)2.4 The ’Tools’ Button
So far, every button we’ve described along the top of the page dealswith the Linux Kernel Device Driver. Not this one. If you press the“Tools” button, or the Tools|Tools menu option, you’ll get a panel thatlooks like,
So, this brings up the question, what does this panel do? Well, ifyou look at the “Stylus Tools”, which appears at the bottom of everypage, you’ll notice that they are the same buttons, just in a verysmall vertical panel. That’s because, the purpose of these buttons isfairly central to how you use the tablet with X client applications.You’ll find yourself wanting to switch your tablet’s behavior from thatof a pen to an airbrush, etc., so often that you’ll have the TabletManager running at the same time.
That’s a good thing, but, as small as we made the pages, you probablywant more screen space allocated to your drawing program. So, here is thisvery small panel. You bring the “Tools” panel up, minimize the TabletManager main page(s), and you’re in business. Of course, if you want toreturn to the main pages, press the “Main App” button. We’ll describewhat it means to behave like an Eraser later, when talking about theX Server Driver functions.2.5 The “Help” Button
Right now, this will present to you the Help|About panel. It’s a listing of people to blame for the Tablet Manager. As always, we gratefullyaccept patches.2.6 The “Quit” Button
It does what you would expect. And no, it doesn’t care whetheryou’ve remembered to save your changes to the tablet, the LinuxKernel Device Driver, or the X Server Device Driver. This isn’t a word processor; hopefully your not writing your PhD thesis with the Gaiptek Tablet Manager.2.7 The “Stylus Tools” Buttons
These buttons are located along the bottom of every page of the mainTablet Manager screens. Similar to the toolbar buttons, these buttons affectis mostly seen in how the tablet currently behaves in conjunction with the XServer Device Driver. E.g., does the stylus behave like a pen, pencil,etc.? We’ll describe what that means later. For now, you should notethat these are push buttons: whichever mode your tablet is in, theappropriate button is shown as being depressed.3. The Linux Kernel Driver Pages3.1 The Info Page
As it has been awhile since you’ve last seen it, here is what theInfo page looks like, below. The Info Page describes attributes ofyour tablet, as determined from the Linux Kernel Device Driver.
You might be wondering, why are we displaying all of thisinformation? Well, when things go wrong, the more information you haveat hand, the easier it is to diagnose what happened, and what to do.Such as, what? Well, without giving away a lot of what’s described inthe Diagnostics section, we’ll just tell you that digital tabletslook a lot like mice and joysticks to other device drivers. And,because of the macro keys along the top of the drawing area, which wesupport, the tablet looks a bit like a keyboard.. So, what if one ofthese other drivers get confused? Hence, the Info page.3.1.2 Size
This shows how big the tablet’s physical drawing area is, in eithercoordinates, inches or millimeters. This is the best way to determinewhether there is any communication issues between the tablet and USBsubsystem/Linux Kernel. How is that? Well, if your tablet suddenlyreports that it’s drawing area is 100x100 coordinates, you know you arein trouble.3.1.3 Manufacturer
This is a string representation of the tablet’s manufacturer.3.1.4 Product
This is a string representation of the tablet’s model. Razer cortex screen recorder. In additionto telling you if there are any communication issues, looking at thesize of the tablet is also the best way to determine what model oftablet is connected. Why do we say that? Well, the screenshot above isof the author’s APT-8000U; several tablet models have been known toshare model identifiers with other Aiptek models. More recent tabletswill return a generic model identifier.3.1.5 Input Path
We mentioned before that Linux does not assign device driver entryname to your tablet based on the connector, like it does for theRS-232C, or hard disc interface. Instead, it will dole out deviceentries dynamically, based on the order in which device drivers areloaded/initialized during boot up, and/or the availability of entrynames when the tablet is hot-plugged into the system.
What this means is, today your tablet might have /dev/input/event1assigned to it. Tomorrow, it might be /dev/input/event7. If you plug anunplug hot-pluggable USB devices, like your tablet, mice and joysticks,there’s more variance.
Also, it does no good to predict where the tablet will be mappedbased on order of device driver modules are loaded, hardware isrecognized, etc. There is movement afoot to speed up the boot cycle ofLinux. What that means is, device drivers that used to wait for oneanother to initialize sequentially no longer do so. Where they can,they’ll load and initialize in parallel with each other, which makesdetermining the order that they’ll complete (and be assigned a deviceentry) hard to determine.
So, you might like to know the device entry that has been assignedto your tablet. Programs like gpm and the X Server tend to show aninterest in this information. Note that our interface to udevtends to resolve this issue by ensuring that there is a softlinkcalled /dev/input/aiptek, which will point to the device entry wherethe tablet’s data is being routed to.3.1.6 VendorID
This is the manufacturer code, shown in hexadecimal.3.1.7 ProductID
This is the product code, show in hexadecimal. Note what we saidabout reuse of product codes.3.1.8 ModelCode
More appropriately, the sub-model ID, in hexadecimal. Also tends tonot be unique among the tablets.3.1.9 ODMCode
The ODM Code describes the third party company who producedyour tablet for the manufacturer. You will find that this helps isolatewhich manufacturing batch your tablet belongs to.3.1.10 Firmware Code
The version of the firmware/BIOS installed on your tablet, inhexadecimal.3.2 The “Settings” Page
That’s enough dry information for now. Moving to the Settingspage, we now have controls that map to attributes of the Linux KernelDevice Driver, and the tablet itself.3.2.1 Pointer Mode Control
This series of buttons allow you to control from which device inputreports will be accepted from. Your tablet comes with both a Stylus anda Mouse which can be used along the drawing surface of the tablet.
If, for example, you specify that you only want input reports fromthe Stylus, that means that all reports from the Mouse will be filteredout. That’s useful, if you placed the Mouse too near your drawing area,and you are getting input reports from it.
By default the Linux Kernel Device Driver accepts reports fromeither device.
The information presented by this control is the same as that keptin the pointer_mode file. (Seethe section on the Linux Kernel DeviceDriver.)3.2.2 Coordinate Mode Control
This series of buttons allow you to control whether the tabletreturns relative coordinate motion reports or absolute coordinatemotion reports. The difference between the two is fairly simple: if thestylus is at location 100,100 on the drawing area, and you move it tothe left 5 coordinates, the stylus moves -5 coordinates along the Xaxis in relative mode, and to 95,100 in absolute mode.
The X Server Driver’s absolute/relative setting is kept independentfrom this, the Linux Kernel Device Driver’s setting. (How? The X ServerDriver will convert relative coordinate reports from the tablet intoabsolute reports, if needed.)
The information presented by this control is the same as that keptin the coordinate_mode file.(See the section on the Linux KernelDevice Driver.)3.2.3 Jitter
This is a delay, following the pressing or depressing of a button onthe Stylus or Mouse, during which all input events from the tablet areignored. Especially with respect to the Stylus, when pressing one ofthe buttons, the chances of the tip moving as your hand steadies itselfis fairly high. During that time, the stylus can otherwise sendspurious input reports. This is a text entry control, and acceptspositive numeric values, in milliseconds.
Obviously, to disable the Jitter timer, set it to 0 milliseconds.
The information presented by this control is the same as that keptin the jitter file. (See thesection on the Linux Kernel Device Driver.)3.2.4 Programmatic Delay
When programming the tablet, there is a delay specified in thecommunications protocol. What we’ve noticed is that certain tabletsprefer differing length of delays. 400ms and 50ms have been seen asprevalent, and indeed, the Linux Kernel Device Driver attempts todetermine the optimal setting during boot time.
The information presented by this control is the same as that keptin the delay file. (See thesection on the Linux Kernel Device Driver.)3.3 The “Mapping” Page
The Mapping Page allows you to inspect and set what sequences theStylus buttons and the Mouse buttons send when pressed. By default, theMouse’s left button will send the Mouse Left Button sequence whenpressed. But, you can change that so it instead sends the rightbutton’s sequence, or the middle button’s. Same thing for the Stylus.No, you cannot map the Stylus buttons to send Mouse button sequences!3.3.1 Stylus Button Mapping
Well, we sort of ruined the surprise above. Except, we should note,both the upper and lower Stylus buttons must be mapped to return somesequence, and no, they cannot both return the same sequence. (Why? Itjust makes good sense.)
These controls correspond to the stylus_lowerand stylus_upper files kept bythe Linux Kernel Device Driver.3.3.2 Mouse Button Mapping
Very much the same as the Stylus buttons, except there are three ofthem, and setting/resetting of sequences might be very useful to theleft-handed.
These controls correspond to the mouse_left,mouse
https://diarynote-jp.indered.space
Aiptek Hyperpen USB tablet drivers for Linux and X.Org/XFree86. Also includes GUI front-end for configuring the tablet while in-use. Supports Aiptek 6000U, 8000U, 12000U. May work with 4000U/5000U, also reported to work with off-brand clones such as LT95.
(interrupt to exit) ^C trak@. Input$ uname -a Linux traktir.trak.spb.ru 2.6.4 #3 Wed Mar 24 13:35:02 MSK 2004 i686 unknown trak@. Input$ /sbin/modinfo aiptek author: Bryan W. Headley/Chris Atenasio description: Aiptek HyperPen USB Tablet Driver (Linux 2.6.x) license: GPL parm: programmableDelay:delay used during tablet programming parm. Downloads 6 Drivers and Manual for Aiptek HyperPen 8000U Other Peripherals. Here’s where you can downloads the newest software for your HyperPen 8000U. We support the following digital tablets: Aiptek HyperPen 4000U, 5000U, 6000U, 8000U, and 12000U. Other tablets we have found to be similar enough include, the Trust Wireless Tablet 400, LIFETEC LT9750, and Medion MD9750. The goal in developing these drivers is to provide a usable working environment for the user and tablet under. Download Aiptek HyperPen Drivers for Windows 10 X64 27.40.358.3338 for free here.
Aiptek, Inc, manufacturesand markets the HyperPen series of USB digital tablets. Aiptek does not,however, offer device drivers for Linux, nor for the X Window System runningon Linux. This project addresses that need by developing Linux and X WindowSystem device drivers. Additionally, we develop an X-based TabletManager, that allows the user to query and dynamicallyreconfigure the device driver’s settings, while the tablet is inactive use.
We support the following digital tablets: Aiptek HyperPen 4000U,5000U, 6000U, 8000U, and 12000U. Other tabletswe have found to be similar enough include, the Trust Wireless Tablet 400, LIFETEC LT9750, and Medion MD9750.
Project Goals
The goal in developing these drivers is to provide a usableworking environment for the user and tablet under Linux. Our goalis to deliver a suite of components that is, first, concernedwith supporting your hardware, second, with supporting yourhardware in the most likely user environment you’ll be using -- the X Window System -- and finally, concernedwith providing you with a usable workflow. These components are,
*TheLinux Kernel device driver delivers tablet movement reportsthrough a device driver interface. Additionally, it offers a text-modeinterface, through the sysfs pseudo-file API (procfsunder Linux 2.4.x) to inspect and dynamically reconfigure the driverand/or your tablet. We support Linux 2.6 and 2.4.
*TheX Window Input Driver reports tablet events to theX Window System, permitting X Window applications to work with thetablet. This driver also supports reporting its status and dynamicreconfiguration; the user interface for doing so is none other than,
*TheTablet Manager presents reports from the Kerneland X Window device drivers in an easy-to-read format for the end user.Settings for both drivers can be inspected and dynamically reconfiguredfrom the Tablet Manager.
The Gaiptek Tablet Manager is a front-end to the programmatic featuresfound in the Linux Kernel Device Driver and the X11 Input Driver. Withthe Tablet Manager, you can inspect and dynamically program the tablet,as well as inspect and modify the behavior of the two drivers. Doing sodoes not mean you have to reboot or reload the driver, nor do you have torestart the X Server.
Having the Gaiptek Tablet Manager running does not affect the normaluse of your tablet: you can have it active while running otherapplications. It won’t affect the tablet or its driver’s behavior until you reprogram them.
Both the Kernel and X Server Drivers support bidirectional interactionwith the user. The X Server Driver uses the Tablet Manager as the front-endto its programmatic interface. The Linux Kernel driver natively supportsa file-oriented user interface, through the sysfs (or procfs on Linux2.4.x) virtual file system. We believe you’ll find the file-orientedinterface useful in batch processing, but will use this interface the majority of the time.
The Tablet Manager is actually three programs in one. One section of theprogram communicates with the Kernel Driver. The other communicates with theX Server Input Driver. The remaining section provides diagnostics for your tablet. Along those lines, we attempted to break down the screens by their function.
Looking at the main screen, you’ll notice that we have set up a tab controlalong the left side of the screen. Those tabs control whether you see Kernel-,X Server-, or Diagnostics-related screens. The left-handed tab controls appearon every page.
But those are not the only controls that appear on every page. The menubar and associated toolbar appears on every page, as well as the series of buttonscalled the ’Stylus Tools’ appears on every page, at the same location.
The controls along the top of the screen are Kernel Driver-related; thebottom controls are Kernel Driver-related, although you’ll mostly see theiraffect through the X Server Driver. The point is, the two drivers are veryinterdependent: someone wanting to configure one driver may well want to alsowork with the other driver.1. Which Tablet Is Being Managed?
The first control is something that’s not very apparent at first –the Window’s title decoration. We use it to convey which tablet you areinspecting and/or programming.
One of the problems we have, when supporting multiple tablets, isconveying which tablet is presently being viewed and/or modifiedto you in an obviousway. The Linux Kernel does not assign device driver entries for USBinput devices in the same way as it does for RS-232C. E.g., there is no/dev/tty01 that always refers to the device connected to the firstserial port. And, should no device be attached to the given serial port,the device entry will still exists in /dev.
Instead, for input devices, the kernel might assign adevice entry like, /dev/input/event5, to your tablet. But even then,that device entry assignment is transitory: it can change everytime you reboot your system. (There is background on this that we’lldiscuss later.)
We get around this issue by displaying the USBconnector that’s physically attached to your tablet. If you lookat thetitle bar shown below, we display that information, much like otherprograms will display the name of the file they are editing.
2. The “Button” Controls
You’ll notice in the above picture, that there are a series ofbuttons going along the top of the page. These buttons appear on allpages of the Tablet Manager.2.1 The “Open Tablet” Button
Knowing what we now know about the Window’s title, and how we addresstelling you which tablet is being presented, you might wonder how to have theTablet Manager deal with your other tablet(s). That’s easy – press the“Open Tablet” button, or choose Tablet|Open Tablet from the menu, and you will see thefollowing panel:
And as you might expect, the pull-down has the list of Aiptektablets controlled by the Linux Kernel Device Driver, identified by theUSB connector they are attached to. Merely choose the correct tablet,and press the “OK” button. The panel disappears, and the Tablet Managerdisplays information about the new tablet.
Now, if you only have one tablet, do you need to go through theprocess of selecting and opening a tablet? No, (and also, No, if youhave more than one) the Tablet Manager will automatically find and openthe first Aiptek tablet it finds.
Of course, if you were in the process of reconfiguring the previoustablet, and did not yet go through the process of reprogramming itfirst, you’ll lose your changes. Which is why there is a “Cancel”button. But it does beg the question, how do you program your tablet?2.2 The “Program” Button
If you are in the process of modifying your tablet’s configuration,or the Linux Kernel Device Driver’s configuration, you might move theTablet Manager from page to page, setting the parameters you wantchanged. And then, when satisfied, you’ll want to program the tablet.This is what the “Program” button, or the Tablet|Program menu option,does for you.
(As you will later see, there is another “Program” Button elsewherein the Tablet Manager, so let us stress: the one along the top of the screen deals with the LinuxKernel Device Driver. Don’t set attributes for the X Server Driver andexpect this button to program them for you. It won’t. It just programs theKernel Driver’s attributes. No harm will come of it ifyou do, but we’d like to avoid frustrating you if we can.)2.3 The ’Refresh’ Button
While inspecting/setting attributes from the Linux Kernel DeviceDriver, you might decide that you want to throw away your changes, andhave the Tablet Manager, instead of showing your pending changes,instead re-present the tablet’s and Linux Kernel Driver’s current state. Howto do this? With the “Refresh” button, or the Tablet|Refresh menu option.
(Again, this refreshes attributes from the Linux Kernel DeviceDriver. Not from the X Server Driver. And yes, there is another“Refresh” button, but it only appears on the X Server page. We’lldiscuss that later.)2.4 The ’Tools’ Button
So far, every button we’ve described along the top of the page dealswith the Linux Kernel Device Driver. Not this one. If you press the“Tools” button, or the Tools|Tools menu option, you’ll get a panel thatlooks like,
So, this brings up the question, what does this panel do? Well, ifyou look at the “Stylus Tools”, which appears at the bottom of everypage, you’ll notice that they are the same buttons, just in a verysmall vertical panel. That’s because, the purpose of these buttons isfairly central to how you use the tablet with X client applications.You’ll find yourself wanting to switch your tablet’s behavior from thatof a pen to an airbrush, etc., so often that you’ll have the TabletManager running at the same time.
That’s a good thing, but, as small as we made the pages, you probablywant more screen space allocated to your drawing program. So, here is thisvery small panel. You bring the “Tools” panel up, minimize the TabletManager main page(s), and you’re in business. Of course, if you want toreturn to the main pages, press the “Main App” button. We’ll describewhat it means to behave like an Eraser later, when talking about theX Server Driver functions.2.5 The “Help” Button
Right now, this will present to you the Help|About panel. It’s a listing of people to blame for the Tablet Manager. As always, we gratefullyaccept patches.2.6 The “Quit” Button
It does what you would expect. And no, it doesn’t care whetheryou’ve remembered to save your changes to the tablet, the LinuxKernel Device Driver, or the X Server Device Driver. This isn’t a word processor; hopefully your not writing your PhD thesis with the Gaiptek Tablet Manager.2.7 The “Stylus Tools” Buttons
These buttons are located along the bottom of every page of the mainTablet Manager screens. Similar to the toolbar buttons, these buttons affectis mostly seen in how the tablet currently behaves in conjunction with the XServer Device Driver. E.g., does the stylus behave like a pen, pencil,etc.? We’ll describe what that means later. For now, you should notethat these are push buttons: whichever mode your tablet is in, theappropriate button is shown as being depressed.3. The Linux Kernel Driver Pages3.1 The Info Page
As it has been awhile since you’ve last seen it, here is what theInfo page looks like, below. The Info Page describes attributes ofyour tablet, as determined from the Linux Kernel Device Driver.
You might be wondering, why are we displaying all of thisinformation? Well, when things go wrong, the more information you haveat hand, the easier it is to diagnose what happened, and what to do.Such as, what? Well, without giving away a lot of what’s described inthe Diagnostics section, we’ll just tell you that digital tabletslook a lot like mice and joysticks to other device drivers. And,because of the macro keys along the top of the drawing area, which wesupport, the tablet looks a bit like a keyboard.. So, what if one ofthese other drivers get confused? Hence, the Info page.3.1.2 Size
This shows how big the tablet’s physical drawing area is, in eithercoordinates, inches or millimeters. This is the best way to determinewhether there is any communication issues between the tablet and USBsubsystem/Linux Kernel. How is that? Well, if your tablet suddenlyreports that it’s drawing area is 100x100 coordinates, you know you arein trouble.3.1.3 Manufacturer
This is a string representation of the tablet’s manufacturer.3.1.4 Product
This is a string representation of the tablet’s model. Razer cortex screen recorder. In additionto telling you if there are any communication issues, looking at thesize of the tablet is also the best way to determine what model oftablet is connected. Why do we say that? Well, the screenshot above isof the author’s APT-8000U; several tablet models have been known toshare model identifiers with other Aiptek models. More recent tabletswill return a generic model identifier.3.1.5 Input Path
We mentioned before that Linux does not assign device driver entryname to your tablet based on the connector, like it does for theRS-232C, or hard disc interface. Instead, it will dole out deviceentries dynamically, based on the order in which device drivers areloaded/initialized during boot up, and/or the availability of entrynames when the tablet is hot-plugged into the system.
What this means is, today your tablet might have /dev/input/event1assigned to it. Tomorrow, it might be /dev/input/event7. If you plug anunplug hot-pluggable USB devices, like your tablet, mice and joysticks,there’s more variance.
Also, it does no good to predict where the tablet will be mappedbased on order of device driver modules are loaded, hardware isrecognized, etc. There is movement afoot to speed up the boot cycle ofLinux. What that means is, device drivers that used to wait for oneanother to initialize sequentially no longer do so. Where they can,they’ll load and initialize in parallel with each other, which makesdetermining the order that they’ll complete (and be assigned a deviceentry) hard to determine.
So, you might like to know the device entry that has been assignedto your tablet. Programs like gpm and the X Server tend to show aninterest in this information. Note that our interface to udevtends to resolve this issue by ensuring that there is a softlinkcalled /dev/input/aiptek, which will point to the device entry wherethe tablet’s data is being routed to.3.1.6 VendorID
This is the manufacturer code, shown in hexadecimal.3.1.7 ProductID
This is the product code, show in hexadecimal. Note what we saidabout reuse of product codes.3.1.8 ModelCode
More appropriately, the sub-model ID, in hexadecimal. Also tends tonot be unique among the tablets.3.1.9 ODMCode
The ODM Code describes the third party company who producedyour tablet for the manufacturer. You will find that this helps isolatewhich manufacturing batch your tablet belongs to.3.1.10 Firmware Code
The version of the firmware/BIOS installed on your tablet, inhexadecimal.3.2 The “Settings” Page
That’s enough dry information for now. Moving to the Settingspage, we now have controls that map to attributes of the Linux KernelDevice Driver, and the tablet itself.3.2.1 Pointer Mode Control
This series of buttons allow you to control from which device inputreports will be accepted from. Your tablet comes with both a Stylus anda Mouse which can be used along the drawing surface of the tablet.
If, for example, you specify that you only want input reports fromthe Stylus, that means that all reports from the Mouse will be filteredout. That’s useful, if you placed the Mouse too near your drawing area,and you are getting input reports from it.
By default the Linux Kernel Device Driver accepts reports fromeither device.
The information presented by this control is the same as that keptin the pointer_mode file. (Seethe section on the Linux Kernel DeviceDriver.)3.2.2 Coordinate Mode Control
This series of buttons allow you to control whether the tabletreturns relative coordinate motion reports or absolute coordinatemotion reports. The difference between the two is fairly simple: if thestylus is at location 100,100 on the drawing area, and you move it tothe left 5 coordinates, the stylus moves -5 coordinates along the Xaxis in relative mode, and to 95,100 in absolute mode.
The X Server Driver’s absolute/relative setting is kept independentfrom this, the Linux Kernel Device Driver’s setting. (How? The X ServerDriver will convert relative coordinate reports from the tablet intoabsolute reports, if needed.)
The information presented by this control is the same as that keptin the coordinate_mode file.(See the section on the Linux KernelDevice Driver.)3.2.3 Jitter
This is a delay, following the pressing or depressing of a button onthe Stylus or Mouse, during which all input events from the tablet areignored. Especially with respect to the Stylus, when pressing one ofthe buttons, the chances of the tip moving as your hand steadies itselfis fairly high. During that time, the stylus can otherwise sendspurious input reports. This is a text entry control, and acceptspositive numeric values, in milliseconds.
Obviously, to disable the Jitter timer, set it to 0 milliseconds.
The information presented by this control is the same as that keptin the jitter file. (See thesection on the Linux Kernel Device Driver.)3.2.4 Programmatic Delay
When programming the tablet, there is a delay specified in thecommunications protocol. What we’ve noticed is that certain tabletsprefer differing length of delays. 400ms and 50ms have been seen asprevalent, and indeed, the Linux Kernel Device Driver attempts todetermine the optimal setting during boot time.
The information presented by this control is the same as that keptin the delay file. (See thesection on the Linux Kernel Device Driver.)3.3 The “Mapping” Page
The Mapping Page allows you to inspect and set what sequences theStylus buttons and the Mouse buttons send when pressed. By default, theMouse’s left button will send the Mouse Left Button sequence whenpressed. But, you can change that so it instead sends the rightbutton’s sequence, or the middle button’s. Same thing for the Stylus.No, you cannot map the Stylus buttons to send Mouse button sequences!3.3.1 Stylus Button Mapping
Well, we sort of ruined the surprise above. Except, we should note,both the upper and lower Stylus buttons must be mapped to return somesequence, and no, they cannot both return the same sequence. (Why? Itjust makes good sense.)
These controls correspond to the stylus_lowerand stylus_upper files kept bythe Linux Kernel Device Driver.3.3.2 Mouse Button Mapping
Very much the same as the Stylus buttons, except there are three ofthem, and setting/resetting of sequences might be very useful to theleft-handed.
These controls correspond to the mouse_left,mouse
https://diarynote-jp.indered.space
コメント