Yeah, this was frustrating me too. Wanted to fix by enabling Users to optionally configure key remapping x=nop, am also looking deeper into the code to see if shortcuts can be disabled while User is actively typing in the console. Auto uppercase some known commands would be nice too. Eventually, I’ll get to cut some wood…
What’s the ideal key shortcut for still enabling triggering X homing? Maybe touch UI and macros are sufficient, no need for keyboard shortcut? Maybe something that can’t be accidentally pressed, but maybe something that does NOT cause RSI? So, no to Ctrl+Shift+Alt+X
Ctrl+ mappings are common at the application level. But Ctrl+x might get captured by the browser already, because of cut, copy, paste. I would suggest Alt+x,y,z. Those are more likely to make it through to the web app.
Okay it seems I think the keys might have actually been mapped wrong. He is replying in github, and showed how all of his GUI’s are the way we want. So bare minimum, I think those could get swapped.
I’m glad the wifi is worth it, it will bring the board cost down significantly.
The keyboard does seem like an easy fix, if he really doesn’t want to change the key map I think we can piece together a long term fix. I understand better why you want to use it, I am sure if I get a dedicated shop computer out here the keyboard would be ideal, that is why I bought it.
Getting close.
P.S. Aaron, I hope you don’t mind I jumped in your git PR, I donated to him a couple weeks back so I figured my name might get it a bit more attention. Feel free to let me know if I am steering it wrong.
In the same tab you run your gcode from. There are three files (4?) on the board itself one is the gz file. I think you need to select onboard instead of SD card.
@azab2c thanks for this man, I really appreciate it.
Looks like I can add nop to y and z too, and also remap the jog distance keys from 1, 2, 3 to F1, F2 F3, for the same reasons I wanted to change the X command. Using those numbers in the terminal changes the units of movement in the jog and could lead to issues with z axis (since jogging that ‘100’ is a recipe for trouble)
Updated my ESP3D WebUI’s edits at <12/28 EDIT: TODO: 12/28 Add link to latest index.html.gz>, and submitted the following changes in pull request for ESP3D folks to consider integrating.
Changes:
Existing/remapped keyshorts now get disabled while you’re actively typing text into the terminal text field, or any other text field. So, with this you don’t need to use NOP even, but still can if you want to for some reason(s) I’m not thinking of. Should now be able to type x/y/z and numbers in the terminal text input field without the page thinking they’re key shortcuts.
After typing gcode text into the Terminal, I use the Tab key to activate shortcuts again, and then Shift+Tab to bring focus back to the Terminal text input field.
Pressing arrow keys when jogging shouldn’t cause the web page to scroll around any more.
Done:
Implemented optional key remapping property for overriding/defining/suppressing key shortcuts:
Agree that Z axis movements should be much smaller than 100, at least for our V1E builds. Should have either a smaller max increment for Z movements, and/or a separate increment scale from XY, thoughts/ideas? Seeing if some existing mechanism/setting is available, ESP3D has lots of config options.
Key remapping setting should support Alt key combo mappings.
Terminal should be smart enough to auto uppercase at least the most common scenarios.
Wifi Access Point config should implement allowing smarter ‘auto’ Wifi channel selection, e.g. during startup, scan available networks and signal strength, then use least occupied channel. Bonus points for optimizing/balancing boot up time by caching last known good channel across resets if scan was done recently.
HowTo: Update ESP3D-WebUI, and configure key remappings
BACKUP your currently working WebUI app…
Browse to ESP3D Dashboard page, look for the Files panel, should see ~4 files listed.
Click on index.html.gz to download a copy of the existing working WebUI app. This is your safety backup that you can upload later on incase you need/want to revert back to original behavior.
Upload a new build of ESP3D WebUI app…
Download the new <12/28 EDIT: TODO: Add link to latest index.html.gz> to your device.
Click on Dashboard page’s Files panel’s down chevron button to find and select Upload File menu option. Select the new index.html.gz file you just downloaded locally.
Refresh the browser to load the updated website pages.
Browse to Settings > Interface tab, scroll around to find key remapping property within the jog panel. Jog panel has lots of settings, so you may need to scroll down within the panel’s content to find.
Edit key remapping field to what makes sense for your build.
Click save changes at bottom of page.
Refresh browser to pickup new settings. Your new keyboard shortcuts should kick in.
Any other helpful changes/enhancements that would maximize User experience for headless, or Wifi enhanced TFT scenarios? Cheers!
So did Luc remap the default keys and is pulling in your changes? I’m not understanding all the changes on github that just happened. I did see the keys are remapped just not sure about the rest, it seems like a lot of changes.
Never mind I see it now. The keyboard key changes have been added to the V3 branch, and you are working together on adding the rest. You guys are writing code so over my head I can barely understand the comments!
Yup, thank you for your input. I would have never found that. The keys are remapped by default and Aaron and Luc are very hard at work implementing the ability to remap keys as you wish. You should take a loot at the github links…so far over my head.