[Bug] Printing Tool Displays Unintuitive Key Labels Instead of Readable Key Names

[jeffersonjpr]

Describe the Bug

Default tool key labels:

Example from Chrome's Print Feature:

QMK Configurator print feature:

Additional Context?

No response

[yanfali]

Sorry. Could you give more context. Which one is your preference? Unintuitive is somewhat subjective so it's difficult to understand. Maybe some annotation around which representation you think is problematic and some possible solutions.

[jeffersonjpr]

I apologize if my explanation wasn't clear. Please take a look at these two keys:

The behavior is: if I hold the key, it activates layer 2; if I just tap it, it triggers other keys.

Notice the difference in how the key behavior is represented in the printing tool. It shows the enum definitions from the code rather than the actual symbols they represent.

The original representation in the configurator is just fine. I think the layout should remain the same in the printing tool.

[yanfali]

Interesting that it's doing that. Maybe it should be a toggle.

[yanfali]

Took some time to look at this today and the issue is how they keys are represented in the printing view. In the visual keymap there are specialized components for each of these container types. In the PrintKey.vue component we just have the single component and it tries it's best to do the right thing for each keycode.

One quick fix, would be to stop printing the QMK code and just show the display version.

If that's acceptable I'll open a PR.

[yanfali]

ok, this should be resolved. I'll close it for now. Thanks.