Author Topic: Easy AVR USB Keyboard Firmware and Keymapper (Read 1376856 times)

bmilcs · « **Reply #2250 on:** Tue, 12 December 2017, 14:23:57 »

https://kbdfans.myshopify.com/products/kbd75-keyboard-set

Does this help?

metalliqaz · « **Reply #2251 on:** Tue, 12 December 2017, 14:39:44 »

Quote from: bmilcs on Tue, 12 December 2017, 14:23:57

https://kbdfans.myshopify.com/products/kbd75-keyboard-set

Does this help?

Yeah that should be good enough. If it's an AVR and code is on github then I can work it out. I'll need you to help me test, though.

bmilcs · « **Reply #2252 on:** Tue, 12 December 2017, 16:19:13 »

Quote from: metalliqaz on Tue, 12 December 2017, 14:39:44

Quote from: bmilcs on Tue, 12 December 2017, 14:23:57
https://kbdfans.myshopify.com/products/kbd75-keyboard-set

Does this help?
Yeah that should be good enough. If it's an AVR and code is on github then I can work it out. I'll need you to help me test, though.

Absolutely

Am I out of luck for AVR & my Southpaw 65 based on TMK

metalliqaz · « **Reply #2253 on:** Tue, 12 December 2017, 19:41:33 »

Quote from: bmilcs on Tue, 12 December 2017, 14:23:57

https://kbdfans.myshopify.com/products/kbd75-keyboard-set

Does this help?

Okay, this might work: easykeymap_windows_kbd75_test.zip

bmilcs · « **Reply #2254 on:** Wed, 13 December 2017, 09:11:26 »

Thanks man! I'm going to test it today after work

Edit: How did you want me to test it? By simply compiling it and testing the stock firmware you put on here?

metalliqaz · « **Reply #2255 on:** Wed, 13 December 2017, 09:49:37 »

Quote from: bmilcs on Wed, 13 December 2017, 09:11:26

Thanks man! I'm going to test it today after work

Edit: How did you want me to test it? By simply compiling it and testing the stock firmware you put on here?

Just use it as you normally would. Create a layout and program it. KBD75 is very similar to the GH60 so I think it will work, but I'm not sure that I have the bottom row mapped right, especially the space.

You never have to compile anything with EasyAVR, just build and burn. I should note, though, that if they have installed a different bootloader then it won't work.

bmilcs · « **Reply #2256 on:** Wed, 13 December 2017, 18:57:54 »

You nailed it minus one key -- top right corner "Pause".

Thanks again for your hard work

bmilcs · « **Reply #2257 on:** Wed, 13 December 2017, 18:59:08 »

Quote from: bmilcs on Wed, 13 December 2017, 18:57:54

You nailed it minus one key -- top right corner "Pause".

Thanks again for your hard work

NEVERMIND. I forgot I set that hotkey as "Boot". Works flawlessly!

metalliqaz · « **Reply #2258 on:** Wed, 13 December 2017, 19:01:25 »

Quote from: bmilcs on Wed, 13 December 2017, 18:59:08

Quote from: bmilcs on Wed, 13 December 2017, 18:57:54
You nailed it minus one key -- top right corner "Pause".

Thanks again for your hard work

NEVERMIND. I forgot I set that hotkey as "Boot". Works flawlessly!

Cool. Now, does that board have any Lock LEDs? Also, what does it have for backlights? Is there RGB?

bmilcs · « **Reply #2259 on:** Wed, 13 December 2017, 19:04:32 »

Quote from: metalliqaz on Wed, 13 December 2017, 19:01:25

Quote from: bmilcs on Wed, 13 December 2017, 18:59:08
Quote from: bmilcs on Wed, 13 December 2017, 18:57:54
You nailed it minus one key -- top right corner "Pause".

Thanks again for your hard work

NEVERMIND. I forgot I set that hotkey as "Boot". Works flawlessly!
Cool. Now, does that board have any Lock LEDs? Also, what does it have for backlights? Is there RGB?

It has under PCB LED's built in. I believe you can add switch LED's as well.

metalliqaz · « **Reply #2260 on:** Wed, 13 December 2017, 19:05:19 »

Quote from: bmilcs on Wed, 13 December 2017, 19:04:32

Quote from: metalliqaz on Wed, 13 December 2017, 19:01:25
Quote from: bmilcs on Wed, 13 December 2017, 18:59:08
Quote from: bmilcs on Wed, 13 December 2017, 18:57:54
You nailed it minus one key -- top right corner "Pause".

Thanks again for your hard work

NEVERMIND. I forgot I set that hotkey as "Boot". Works flawlessly!
Cool. Now, does that board have any Lock LEDs? Also, what does it have for backlights? Is there RGB?

It has under PCB LED's built in. I believe you can add switch LED's as well.

Do they work?

jacob.stadtfeld · « **Reply #2261 on:** Fri, 15 December 2017, 00:16:08 »

Don't suppose this is the place to make a request for a new keyboard layout? I'm working with a Cherry SPOS G86-63401.

metalliqaz · « **Reply #2262 on:** Fri, 15 December 2017, 08:28:13 »

Quote from: jacob.stadtfeld on Fri, 15 December 2017, 00:16:08

Don't suppose this is the place to make a request for a new keyboard layout? I'm working with a Cherry SPOS G86-63401.

EasyAVR only works on custom keyboards with AVR microcontrollers.

To program that Cherry SPOS you would use the tools provided by the manufacturer.

bmilcs · « **Reply #2263 on:** Sun, 17 December 2017, 15:08:15 »

Quote from: metalliqaz on Wed, 13 December 2017, 19:05:19

Quote from: bmilcs on Wed, 13 December 2017, 19:04:32
Quote from: metalliqaz on Wed, 13 December 2017, 19:01:25
Quote from: bmilcs on Wed, 13 December 2017, 18:59:08
Quote from: bmilcs on Wed, 13 December 2017, 18:57:54
You nailed it minus one key -- top right corner "Pause".

Thanks again for your hard work

NEVERMIND. I forgot I set that hotkey as "Boot". Works flawlessly!
Cool. Now, does that board have any Lock LEDs? Also, what does it have for backlights? Is there RGB?

It has under PCB LED's built in. I believe you can add switch LED's as well.
Do they work?

Sorry just got around to recreating my layout within EasyAVR. But I'm having trouble figuring out how to create these keys:

LT(1, TAB)

So, holding it down is FN1 and tap = TAB key.

Is this possible in EasyAvr?

I tried setting the GUI Tab to FN1 and then Mode: Tap Key - TAB

metalliqaz · « **Reply #2264 on:** Sun, 17 December 2017, 17:09:35 »

Quote from: bmilcs on Sun, 17 December 2017, 15:08:15

Quote from: metalliqaz on Wed, 13 December 2017, 19:05:19
Quote from: bmilcs on Wed, 13 December 2017, 19:04:32
Quote from: metalliqaz on Wed, 13 December 2017, 19:01:25
Quote from: bmilcs on Wed, 13 December 2017, 18:59:08
Quote from: bmilcs on Wed, 13 December 2017, 18:57:54
You nailed it minus one key -- top right corner "Pause".

Thanks again for your hard work

NEVERMIND. I forgot I set that hotkey as "Boot". Works flawlessly!
Cool. Now, does that board have any Lock LEDs? Also, what does it have for backlights? Is there RGB?

It has under PCB LED's built in. I believe you can add switch LED's as well.
Do they work?

Sorry just got around to recreating my layout within EasyAVR. But I'm having trouble figuring out how to create these keys:

LT(1, TAB)

So, holding it down is FN1 and tap = TAB key.

Is this possible in EasyAvr?

I tried setting the GUI Tab to FN1 and then Mode: Tap Key - TAB

Yes it's possible and that should work. What part of the mapping isn't working for you?

metalliqaz · « **Reply #2265 on:** Wed, 20 December 2017, 20:36:13 »

A new feature is coming to EasyAVR. I have added a simple tool that can help you add support for new boards using input from keyboard-layout-editor.com.

It still takes some work with a text editor, because the data from keyboard-layout-editor.com doesn't contain any information about the IO pins that are used for the row/column matrix or LEDs. However it's still a good shortcut.

JustCallMeCrash · « **Reply #2266 on:** Thu, 21 December 2017, 06:07:45 »

I haven't read through the whole thread (shoot me), but is there any chance Preonic support may be added? It would sure be nice to have a good gui for programming my flatboard of choice (I spend 95% of my time on ErgoDoxen).

metalliqaz · « **Reply #2267 on:** Thu, 21 December 2017, 08:17:44 »

Quote from: JustCallMeCrash on Thu, 21 December 2017, 06:07:45

I haven't read through the whole thread (shoot me), but is there any chance Preonic support may be added? It would sure be nice to have a good gui for programming my flatboard of choice (I spend 95% of my time on ErgoDoxen).

According to this page, the new Preonic boards come with the QMK bootloader. I'm pretty sure it won't load my firmware. If the rev1 pcb uses the standard USB bootloader, then that could work.

bmilcs · « **Reply #2268 on:** Thu, 21 December 2017, 19:55:30 »

Update - The KBD75 firmware seems to work great but the LED options don't seem to do anything. For whatever reason, only the top left LED is lit up (underneath the PCB).

Can you fix this by any chance?

metalliqaz · « **Reply #2269 on:** Fri, 22 December 2017, 09:47:22 »

Quote from: bmilcs on Thu, 21 December 2017, 19:55:30

Update - The KBD75 firmware seems to work great but the LED options don't seem to do anything. For whatever reason, only the top left LED is lit up (underneath the PCB).

Can you fix this by any chance?

Probably because the KBD75 has RGB backlighting. I don't own any keyboards with RGB backlighting, so it isn't supported.

I copied the hardware definition from the QMK firmware: https://github.com/qmk/qmk_firmware/blob/master/keyboards/kbd75/config.h

From that, I included pin B6 as a backlight, though I have no idea what purpose it serves on the KBD75.

OfTheWild · « **Reply #2270 on:** Thu, 28 December 2017, 10:45:19 »

Quote from: metalliqaz on Wed, 20 December 2017, 20:36:13

A new feature is coming to EasyAVR. I have added a simple tool that can help you add support for new boards using input from keyboard-layout-editor.com.

It still takes some work with a text editor, because the data from keyboard-layout-editor.com doesn't contain any information about the IO pins that are used for the row/column matrix or LEDs. However it's still a good shortcut.

I'm interested in playing with this as i'd like to add first the JD40 MkII layout with the 6.25 space (i figure this is an easy place for a noob to start) but then i'd love to add in the QMK port for the Duck Lightsaver v3 once i have a better understanding of how.

So yeah, i'd love some more info on this and i'll get started.

metalliqaz · « **Reply #2271 on:** Thu, 28 December 2017, 10:46:56 »

Quote from: OfTheWild on Thu, 28 December 2017, 10:45:19

Quote from: metalliqaz on Wed, 20 December 2017, 20:36:13
A new feature is coming to EasyAVR. I have added a simple tool that can help you add support for new boards using input from keyboard-layout-editor.com.

It still takes some work with a text editor, because the data from keyboard-layout-editor.com doesn't contain any information about the IO pins that are used for the row/column matrix or LEDs. However it's still a good shortcut.

I'm interested in playing with this as i'd like to add first the JD40 MkII layout with the 6.25 space (i figure this is an easy place for a noob to start) but then i'd love to add in the QMK port for the Duck Lightsaver v3 once i have a better understanding of how.

So yeah, i'd love some more info on this and i'll get started.

It's in the readme on Github. It's still takes some hacking, but it a bit quicker

OfTheWild · « **Reply #2272 on:** Thu, 28 December 2017, 11:02:49 »

Quote from: metalliqaz on Thu, 28 December 2017, 10:46:56

Quote from: OfTheWild on Thu, 28 December 2017, 10:45:19
Quote from: metalliqaz on Wed, 20 December 2017, 20:36:13
A new feature is coming to EasyAVR. I have added a simple tool that can help you add support for new boards using input from keyboard-layout-editor.com.

It still takes some work with a text editor, because the data from keyboard-layout-editor.com doesn't contain any information about the IO pins that are used for the row/column matrix or LEDs. However it's still a good shortcut.

I'm interested in playing with this as i'd like to add first the JD40 MkII layout with the 6.25 space (i figure this is an easy place for a noob to start) but then i'd love to add in the QMK port for the Duck Lightsaver v3 once i have a better understanding of how.

So yeah, i'd love some more info on this and i'll get started.
It's in the readme on Github. It's still takes some hacking, but it a bit quicker

Ok i'll see if i can figure it out - the section about "supporting custom boards" i assume? I'd love to get more involved with this project.

suicidal_orange · « **Reply #2273 on:** Thu, 11 January 2018, 04:30:13 »

Quote from: metalliqaz on Wed, 20 December 2017, 20:36:13

A new feature is coming to EasyAVR. I have added a simple tool that can help you add support for new boards using input from keyboard-layout-editor.com

Just returned from hiatus and tried this - very impressed, it even chose the appropriate sixty/tkl firmware base in case anyone's brave enough to handwire a big board

How are you getting on with your customising OfTheWild?

metalliqaz · « **Reply #2274 on:** Thu, 11 January 2018, 07:34:58 »

Quote from: suicidal_orange on Thu, 11 January 2018, 04:30:13

Quote from: metalliqaz on Wed, 20 December 2017, 20:36:13
A new feature is coming to EasyAVR. I have added a simple tool that can help you add support for new boards using input from keyboard-layout-editor.com

Just returned from hiatus and tried this - very impressed, it even chose the appropriate sixty/tkl firmware base in case anyone's brave enough to handwire a big board

Thanks. My next step will be to record a video of me adding support start to finish when something is requested. The hope is that users can start to do it on their own.

suicidal_orange · « **Reply #2275 on:** Fri, 12 January 2018, 04:06:25 »

^ Sounds good, though it seems pretty self explanatory - maybe I'm biased having played with it manually.

I've just tested adding a new board on a fresh Linux install and got an error about encoding using python 2.7.13 (the one used by default) but it worked when I switched to 3.4.6 - no idea what else I've broken by manually switching though, so please don't add it to the readme...

metalliqaz · « **Reply #2276 on:** Fri, 12 January 2018, 06:53:32 »

Quote from: suicidal_orange on Fri, 12 January 2018, 04:06:25

^ Sounds good, though it seems pretty self explanatory - maybe I'm biased having played with it manually.

I've just tested adding a new board on a fresh Linux install and got an error about encoding using python 2.7.13 (the one used by default) but it worked when I switched to 3.4.6 - no idea what else I've broken by manually switching though, so please don't add it to the readme...

That bug has already been submitted on Github and fixed.

Also, use 3.6 dude. 2.7 is old and busted.

suicidal_orange · « **Reply #2277 on:** Fri, 12 January 2018, 10:18:29 »

Good to know, was only packaged recently so you've been busy

It's a fresh install of Open Suse so surprised it's so out of date - 3.4.6 is the latest (stable?) version available so that will do for now.

metalliqaz · « **Reply #2278 on:** Fri, 12 January 2018, 10:25:34 »

Quote from: suicidal_orange on Fri, 12 January 2018, 10:18:29

Good to know, was only packaged recently so you've been busy

It's a fresh install of Open Suse so surprised it's so out of date - 3.4.6 is the latest (stable?) version available so that will do for now.

Really? Wow. Python 3.7 is already in alpha. I guess OS moves slowly.

suicidal_orange · « **Reply #2279 on:** Fri, 12 January 2018, 10:42:28 »

Hmm, that makes me wonder what else is out of date... Time for a change of distro!

deacon · « **Reply #2280 on:** Mon, 22 January 2018, 08:19:38 »

Quote from: metalliqaz on Thu, 21 December 2017, 08:17:44

Quote from: JustCallMeCrash on Thu, 21 December 2017, 06:07:45
I haven't read through the whole thread (shoot me), but is there any chance Preonic support may be added? It would sure be nice to have a good gui for programming my flatboard of choice (I spend 95% of my time on ErgoDoxen).

According to this page, the new Preonic boards come with the QMK bootloader. I'm pretty sure it won't load my firmware. If the rev1 pcb uses the standard USB bootloader, then that could work.

Jack Humbert says that his new bootloader should be DFU compatible, unfortunately I don't have the new bootloader on anything to test.
https://www.reddit.com/r/olkb/comments/7qht0f/jacks_weekly_update_question_thread_for_2018w03/dsytfd6/

suicidal_orange · « **Reply #2281 on:** Tue, 23 January 2018, 11:46:17 »

Quote from: deacon on Mon, 22 January 2018, 08:19:38

Jack Humbert says that his new bootloader should be DFU compatible, unfortunately I don't have the new bootloader on anything to test.
https://www.reddit.com/r/olkb/comments/7qht0f/jacks_weekly_update_question_thread_for_2018w03/dsytfd6/

That's good - the firmware is available so you can see the pins to use the built in 'Define new keyboard' and add it, you'll also need a KLE export. Metalliqaz was looking for someone to test this, well volunteered

Unrelated - is anyone using this in Linux? I just tried to build and flash and I'm getting the error below on two GH60 boards - one works and the other I've just unwrapped ready to build so it should work. I probably broke my python but no idea how to check, changing debug to a different number changes it at the top but no useful output

Code: [Select]

sudo dfu-programmer atmega32u4 flash --debug 10 Keyboards/EasyAVR-2.05.11/keymapper/GH60.hex
     target: atmega32u4
    chip_id: 0x2ff4
  vendor_id: 0x03eb
    command: flash
      quiet: false
      debug: 10
device_type: AVR
------ command specific below ------
   validate: true
   hex file: Keyboards/EasyAVR-2.05.11/keymapper/GH60.hex

Checking memory from 0x0 to 0x6E7F...  Empty.
0%                            100%  Programming 0x6E80 bytes...
[ X  ERROR
Memory write error, use debug for more info

Will have to try in Windows.

Edit: The hex from Windows is indeed different, but it fails to flash (in Linux) with the same error. Probably a flasher problem...

metalliqaz · « **Reply #2282 on:** Tue, 23 January 2018, 13:10:13 »

Quote from: suicidal_orange on Tue, 23 January 2018, 11:46:17

Edit: The hex from Windows is indeed different, but it fails to flash (in Linux) with the same error. Probably a flasher problem...

Eh, that should not be the case. The build should be identical regardless of platform, as long as you are using the same version of the software and the same map.

I have never programmed with linux so I can't be much help. If you are able to program a file with Windows then that would clear the keymapper of any wrongdoing.

The error message doesn't give us much to work with. Are you sure that the board is staying in bootloader mode?

suicidal_orange · « **Reply #2283 on:** Tue, 23 January 2018, 13:28:32 »

Thinking about it the Windows version has the UTF8 fix so it would be different. Linux has always just worked in the past and I've tried an old hex as well and that doesn't flash either - the finger of blame is definitely pointing at the flasher. Need a new distro with up to date Python as well...

metalliqaz · « **Reply #2284 on:** Tue, 23 January 2018, 13:30:30 »

Okay, good luck, and let me know if you find anything wrong with my stuff. I'm always eager to squish bugs.

suicidal_orange · « **Reply #2285 on:** Tue, 23 January 2018, 16:14:17 »

All good - after upgrading dfu-programmer (which did nothing) force erasing the already erased board made it flash happily. Strange that the unused board behaved exactly the same...

As for bugs can I just check how layers are supposed to work? I thought the FN to return to the default layer was supposed to match the current layer, but putting a Toggle FN3 on layer 3 which is accessed using a Normal FN3 locks the board on layer 3, while FN2 returns to the default layer. As-is there is no way to reliably return to the default layer from a layer that is accessed from two different toggled layers.

Not sure that makes any sense written out but it could be a problem if you're looking for something to fix, I've added pics below which might help explain it.

More

metalliqaz · « **Reply #2286 on:** Tue, 23 January 2018, 19:46:46 »

i'm having trouble following. Let's take it one step at a time.

Start on default layer (L0)
Press Fn to activate Fn Layer (L1)
Press Fn2 to activate and lock L2
Release Fn2
Release Fn
Press Fn3 to activate L3
Press Fn2 to activate and unlock L2
Release Fn2
Release Fn3
L0 should now be active

Is that right?

suicidal_orange · « **Reply #2287 on:** Wed, 24 January 2018, 04:39:37 »

Yes that's how it works and when you put it like that it sounds like it's by sensible design. I guess I misunderstood long ago - hopefully I didn't pass the bad knowledge on! I thought it was:

7. Press Fn3 (current layer) to unlock all and return to L0

The 'problem' is that L1 and L3 are the same and only duplicated so the 'swap layer' button works. I was going to add two number pad layers for the same reason - 'back' needs to go to L0 or L2. This seems such a waste of layers, literally halving what's available.

I don't suppose the firmware knows the layer that was locked before the current one so you could add a 'previous layer' keycode? Not sure how many people would use it...

The more I think the more it sounds like I should just make the jump to Colemak, adding the qwerty layer as a backup with no helpful layers so I can enter passwords using keycap legends when drunk rather than locking myself out

)

metalliqaz · « **Reply #2288 on:** Wed, 24 January 2018, 08:34:00 »

In EasyAVR, there are only three layers in memory:

default_layer (usually L0 but can be changed with the config menu)
locked_layer (set when you use toggle or lockable Fn keys)
selected_layer (set when you use momentary Fn keys)

If you lock a layer and then lock a different layer, locked_layer is replaced and the previous locked layer is lost. If you lock a layer that is already locked, it falls back on the default layer.

This all works great for the way I use keyboards, but if you are used to the Up/Down concept or 'swap layer', it can get confusing. Basically what you want to do when you permanently select a layer is just use a toggle Fn key for the layer you want.

In your case, the main problem seems to be that there is no Fn0 key and it's hard to picture how to get back to Default. I really should add that. People really expect it when moving between permanant layers.

Another unfortunate issue is that the original firmware only had 2 layers: default and Fn. I wish I could go back and rename them to L0 and L1. If I remember correctly, I can't just rename them now because saved layouts would break. I'll look into that too.

suicidal_orange · « **Reply #2289 on:** Wed, 24 January 2018, 09:07:15 »

Fair enough - I'm not used to anything as such but now I understand I'll make it work.

If you can change the default layer you really should have an Fn0 though, otherwise you can't use that layer at all - you've found your own bug!

As to the change of layer names couldn't they be substituted during load? Wouldn't want to do lots of hard coded substitutions but there are only two so could be an option.

metalliqaz · « **Reply #2290 on:** Wed, 24 January 2018, 23:16:59 »

I've made the changes but I still have to test it.

Programming is a good excuse to sit down and listen to some retrowave. Love me some retrowave.

metalliqaz · « **Reply #2291 on:** Sat, 27 January 2018, 08:09:32 »

New Release 2.06.01

Add SCANCODE_FN0 for selecting the default layer if it isn't default
Rename SCANCODE_FN to SCANCODE_FN1
Python 2.7 is no longer supported, switch to Python 3.6

suicidal_orange · « **Reply #2292 on:** Sun, 28 January 2018, 03:18:36 »

Sounds great, except the Python 3.6 bit. Really must upgrade...

metalliqaz · « **Reply #2293 on:** Sun, 28 January 2018, 08:51:57 »

Quote from: suicidal_orange on Sun, 28 January 2018, 03:18:36

Sounds great, except the Python 3.6 bit. Really must upgrade...

2.7 still works, I just don't support it anymore.

kamilakas · « **Reply #2294 on:** Fri, 09 February 2018, 12:33:20 »

Hi, guys. Can someone help me with writing macro like on the screenshot?

metalliqaz · « **Reply #2295 on:** Fri, 09 February 2018, 12:53:31 »

Quote from: kamilakas on Fri, 09 February 2018, 12:33:20

Hi, guys. Can someone help me with writing macro like on the screenshot?

What is that supposed to do? Are you trying to map a key to Alt+Tab? If so, you don't need a macro to do that with EasyAVR.

kamilakas · « **Reply #2296 on:** Fri, 09 February 2018, 13:07:32 »

Quote from: metalliqaz on Fri, 09 February 2018, 12:53:31

Quote from: kamilakas on Fri, 09 February 2018, 12:33:20
Hi, guys. Can someone help me with writing macro like on the screenshot?

What is that supposed to do? Are you trying to map a key to Alt+Tab? If so, you don't need a macro to do that with EasyAVR.

It must "imitate" Alt+Tab then pressed Alt. It's the shortcut for switching windows in Windows (lol). For example, press this "alt+tab", holding it (keycode is Alt, hold). Then you just press default Tab to switch between windows.

metalliqaz · « **Reply #2297 on:** Fri, 09 February 2018, 14:03:48 »

Okay there's definitely a language barrier between us. I think you're trying to either:

1) Map a key to Alt+Tab.

2) Map a key to Alt when held, and Alt+Tab when tapped.

For (1), all you have to do is map the key to Tab, then add a "with modifier" option and select R_Alt.

For (2), that is not currently possible, although it probably should be, and we could add a PR to fix it.

If you want to make a macro of Alt+Tab, you it would look something like this: \ALT(\TAB,)

ErgoMacros · « **Reply #2298 on:** Fri, 09 February 2018, 14:17:45 »

(I didn't read the code, I could be all wet here) I think what he wants is:

Key #1 behavior:
On press does Alt-down, Tab-down, Tab-up (and Alt is still down)
... on release does Alt-up

On tap does Alt-down, Tab-down, Tab-up, Alt up

Key #2: Normal Tab key behavior.
-----
Use:
Key #1-Down and release generates Alt-Tab down and Tab-Alt up == Switch to next app (using a single tap)

Key #1-Down, Key #2 tap, Key #2 tap, Key #1-up == Switch to next app + 2 (with a hold and 2 taps.)

Unusual, perhaps, but it you swap between the 2 front-most apps a lot it would add efficiency, while not eliminating the ability to get to other apps.

metalliqaz · « **Reply #2299 on:** Fri, 09 February 2018, 14:46:33 »

Oh, yes, I think you're right. That makes sense.

This is not currently possible with EasyAVR. The problem is getting one key to act as a modifier and a macro at the same time. Just describing that kind of behavior in the GUI is hard to imagine.


120/100g linear Zealio R1 GMK Hyperfuse 'Split everything' perfection	MX Clear SA Hack'd by Geeks EasyAVR mod

News:

Author Topic: Easy AVR USB Keyboard Firmware and Keymapper (Read 1376856 times)