Keymap write broken for duplicated Layout

[jmwample]

When creating a new keymap layout, if you start by duplicating an existing keymap, and then modifying from there when you go to write your keymap to the keyboard it will write the original configuration, not the modified duplicated version.

Steps to reproduce:

1. Open the agent
2. write a keymap to keyboard
3. duplicate the configuration
   • make any key assignment changes in the new copy of the layout
4. write the updated keymap to the keyboard

At this point the keyboard will still have the original configuration

5. modify the original keymap layout
6. try to write the updated (duplicated) version of the keymap

You can test and see that the original keymap has been written with any updates you made to it in step 5.

There is some bug here with keymap ID collision when a keymap is duplicated.

Workaround

I wanted to use the duplicate keymap to keep a main and an experimental layout. I was able to do this by duplicating the original twice, the first copy is the experimental version, the second copy keeps my original layout. Then I deleted the actual original. This allows the experimental version to be written to the keyboard seemingly without conflicting with the other still existing duplicate.

Context

Agent version: 5.0.2
UHK 80
linux platform (debian family os)
installed from website

[mondalaci]

I couldn't reproduce the issue, but when duplicating my default keymap, it's not selected in the side menu.

@ert78gb Can you reproduce this issue?

[ert78gb]

I left my UHK80 in other city so I could test it on Sunday evening or Monday. Sorry for the delay