Help Wanted: Testing Milton with Wacom clones about milton HOT 22 CLOSED

Drawing is working well on my Monoprice 22HD with my Linux build. Don't have pressure sensitivity right now but that is not a milton issue, it's a problem with the driver I'm currently using

from milton.

I just got confirmation that pressure is working with the driver I am using. I was able to draw with pressure in gimp after changing a setting. I don't have pressure sensitivity in Milton. I don't know whether the driver I am using conforms to the Wacom API or if it is doing something else.

If the driver for my tablet is doing something different and support for it would be non-trivial, I'll either live without pressure or look into adding support for it myself, but if there would be an easy change to get pressure going for me that would be awesome.

Sometimes I accidentally press the side button and it occasionally causes random lines to get drawn on the screen. I know that by default the pen's side button is being mapped to right click, and playing with right-click in milton I see that it acts the same as left click. I'll probably look into mapping it to space at some point and post here again if I still have issues with it

from milton.

I don't know if fixing EasyTab for your driver would be an easy fix or not. I will let you know if I make progress, but right now I can't think of what could be the problem. The code for EasyTab is similar to what GTK does as far as I remember. QT is similar too, but there aren't that many people doing this. Most projects are on top of QT or GTK and don't have to do it.

As for the pen button mapping problem. I want the right click to open a context menu so it can just be disabled for now. I'll fix it and do a commit&push.

from milton.

I am having an issue with my huion h420. I use my tablet to plan my programs and such. Kind of like Casey Muratori does with handmade hero. I actually started using milton recently because one note was not doing it for me anymore. Unfortunately when I draw there is a slight lag that stops me from completing my motion. For example if im trying to draw the letter "e" the loop part of the e will always get cut off. huion is a cheap clone tablet but it is very good for people like me who use it for planning. Milton and this tablet is the perfect combo.

from milton.

I'm also using the Huion H420, but with a different issue. Pressure is working, but I can only draw in the top left corner. Example:

First dot is focus with mouse, rest is tablet

It does interact with the tools up there as well. It tracks the cursor properly but draws improperly.

from milton.

from milton.

@crhallberg Thanks for the gif. If you're able to recompile, you might want to try playing with the InputExtentX, InputExtentY in lines 1001-4 of EasyTab.h. Trying some hard coded values. I would start with

        EasyTab->InputExtentX = [Your monitor's horizontal resolution];
        EasyTab->InputExtentY = [Your monitor's vertical resolution];

and see if that changes anything. Then make it bigger / smaller.
Otherwise I will eventually get one of these and try it out.

from milton.

@GoldbergJarrett And what where you hoping to accomplish by telling me you "had to ditch" Milton?
I'm more than happy to work on bug reports for Milton. Unfortunately I am just one person, and fixing the Huion H420 is low on the priority list. You're free to try out any other drawing app without bothering me about it

from milton.

from milton.

Apologies on my end too. It was wrong to respond with a knee jerk reaction and I regretted it immediately. Really sorry about that.. :)

BTW - I expect Milton won't support pressure sensitivity on the surface pro unless Microsoft implemented support for the Wacom API. As far as I know there are people who use it, though there have been some reports of problems with the Intel integrated graphics. Please let me know if you run into problems.

And again, apologies! Won't happen again.

from milton.

from milton.

Hard-coding my screen resolution works.

Sorry, it took me a while to get the source compiling.

from milton.

The weird thing is the other tablet I used (Wacom) didn't have this problem. So how do we diagnose it?

from milton.

I can't paint anything with Huion 420 graphics tablet. Single clicks are detected on the GUI windows (brushes, layers, ...) via the pen, but not on the canvas. EDIT: This is the same issue as @crhallberg, Sorry.

from milton.

OK, I think I understand what the problem is. PacketBuffer[i].pkX and PacketBuffer[i].pkY are given already scaled (output coordinates), so IMHO the calculations in EasyTab_HandleEvent() are wrong because they're done in input coordinates. Wintab specs. Another option is to scale by EasyTab->RangeX and EasyTab->RangeY.

from milton.

I have Huion H640P and was having same issue as @crhallberg . Hardcoded InputExtent values according to resolution fixed the issue, but I had to multiply X by number or active monitors for some reason. I use 2 monitors at 1920x1080, so this worked for me:

    EasyTab->InputExtentX = 1920 * 2;
    EasyTab->InputExtentY = 1080;

I got the program working, so I didn't pursue proper fix any further.

Awesome program by the way. Compared to most other painting programs Milton feels so responsive. I love my new whiteboard that has practically unlimited size!

from milton.

I implemented my proposed change in a fork. It works for me. People with a wacom tablet, and/or dual monitors, and/or other kinds of tablets - please test my fork. If it's any good, I'll do a PR. Link.

from milton.

@liorda I tested your fork on my H640P and it works fine with my setup. I tested with two monitors and tried switching primary display in display settings and mapping tablet to a different screen in Huion configuration. As long as I restart Milton after making any changes to these configurations, it seems to work as expected.

Hopefully I'll be able to test this with a Wacom setup later today. That machine has double/triple display with varying display sizes and some rather old Intuos Wacom tablet. Testing with Wacom tablet could give some indication if these changes affect Wacom users in some way.

edit: I now tested your fork with Wacom tablet and dual screen setup where tablet was mapped to main screen. It didn't work as expected. Tablet input and all drawings went way off to the right from where the drawing cursor was.

from milton.

@anssilap interesting, thanks for reporting. I wonder if I should have used the "system" data from the packet instead of the "output", because it works for the Huion either way. Maybe I'll be able to test it on a wacom from work later today.

from milton.

Hey @anssilap and @liorda , thanks for your time!

@liorda , I'm looking at your fork. It looks fine to me, I just have a couple comments:

Instead of flipping coordinates for each packet (line 1107), it's probably better to leave the line LogContext.lcOutExtY = -LogContext.lcOutExtY;, which should accomplish the same thing. Am I right? It's been long enough since I touched Wacom code that it's flushed from my brain.

Also, I normally accept PRs and then change the code-style myself, but if you could just align it to four spaces instead of tabs it would be better. No big deal either way.

Anyway, from what I read in the comments it looks like @liorda 's fix works. Thanks a lot everyone!

from milton.

@serge-rgb see @anssilap edit - it didn't work for him on dual screen setup. I just comitted another change. Can you see if it still works for your Wacom? I don't understand how the negation helps. Also changed to spaces.

from milton.

Closing as I get ready for a new release, for which huion tablets should work.

from milton.