I have a sixkeyboard and got Easy AVR installed on it mostly because I need a nice way to do a repetitive macro:
Right click,down,down,enterBut it looks like easy avr does not support macros that use the mouse.
I don't really have a clue what I am doing, python makes me head spin and i've never compiled firmware before (till I made one that temporarily broke my keyboard a few moments ago)
But I was hoping someone could help fill in the gaps.
So, the first part is to get the macro parser to recognize the mouse codes, simple enough.
https://pastebin.com/cnFEURzaBut the problem is that (as best I can tell) this all gets saved, and then ran by autokey.c which shoved the codes directly into enqueue_key, which is only made to report about the keyboard.
(I suspected that this means that macros which use the volume commands that should be supported.. would not work, and my tests confirmed that)
So I figured that there is already a good function to pick what device we are talking about, handle_code_actuate, and it can eventually end up with enqueue_key or something more appropriate like set_mousebutton
https://pastebin.com/B4Y9wJ5PThe issue, is that this is all atmel c code now, which did not like compiling. I was able to switch the board target easily enough, but it is clear that I needed to define __AVR_ATmega16U2__ and BOARD_SIZE_CARD, but I am not really sure how to do this. The compile.bat is out of date I think, I ended up just manually editing the defines, which gave me a build that does not run.
Hope someone has time to help.
Either way, thanks so much for this software, it's the only reason i got the sixkeyboard.
Edit: I just went and tried from a fresh slate again. I still don't know where to find these compile defines in visual studio, but manually editing firmware.cproj seemed to do the trick. Maybe it was just that it wasn't too late at night, but the build is working great for me now. Right clicks and volume adjustments in a macro are working!
Feel free to use the patches for whatever, i would imagine you would get some interesting results if you made macro 1 call macro 1 inside of it.. but I think for most things, possibly safe from an ignorant perspective. I will be doing some more testing.