Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pen Sensitivity #6

Open
martinleopold opened this issue Nov 16, 2017 · 1 comment
Open

Pen Sensitivity #6

martinleopold opened this issue Nov 16, 2017 · 1 comment

Comments

@martinleopold
Copy link

I am experiencing an issue where lighter strokes are clearly visible on paper but are not recognized by the SDK. Only when I press the pen down harder I get stroke data.

Is there a way to change the sensitivity using the penPressure state? What range of values does - (void)setPenStateWithPenPressure:(UInt16)penPressure; accept and what do they mean?

I was also wondering what exactly some of the other pen state properties do, especially useAccelerator and useHover. I use an F110 by the way, so the SDK is version 1.

typedef struct __attribute__((packed)){
    int32_t timezoneOffset;
    UInt64 timeTick;
    UInt32 colorState;
    unsigned char usePenTipOnOff;
    unsigned char useAccelerator;
    unsigned char useHover;
    unsigned char beepOnOff;
    UInt16 autoPwrOnTime;
    UInt16 penPressure;
    unsigned char reserved[16];
} SetPenStateStruct;
@louisjrpark
Copy link
Collaborator

Dear Martin,

Yes, pen sensitivity can be changed by 'setPenStateWithPenPressure'. The range of the value is between 0~4. '0' is the most sensitive.
Regarding useAccelerator and useHover, useHover is for hovering mode like proximity mode which has been used for testing internally in our company. And, useAccelerator is used to wake up the pen which is also being used internally. Thus, both of them should not be used by customers.

Thanks
Best regards,
Louis Park

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants