DWC 2 - Stupid #$%# popup when trying to type console cmds
-
Here's a screen snippet of what I'm referring to. If a user is running in a lower resolution, or a small browser window, the console edit box is completely taken over by that popup showing what I assume are previously entered commands. Covering the edit box is only half the problem. The other half is that the edit box loses focus in favor of the popup. So when a user presses "ENTER", they end up actually executing whatever command the mouse was over instead of what they were typing.
In the below image, I wanted to type a gcode command in the console, but as soon as I started, I instead got that popup. The edit control is completely covered.
-
@garyd9
Rather agree with you on this; having a list of quick/previous commands is handy, but the way it is handled in DWC is quite intrusive, and too proactive in suggesting autocompletions.I sometimes run entire CNC jobs from the console when cutting quick holes in existing panels etc, no need to CAD them or create a gcode file, simple rectangles and circles are only a few lines and quicker to just enter manually. I've never done this from the DWC console, but I imagine it would not be smooth experience.
-
Yup! I manually offset tools initially when getting machines running and the pop up normally covers the z level that I need.
-
The popup is irritating indeed. Makes using the console from a phone close to impossible.
Also, the order of the history is weird. I would expect the last command entered to be on top, which it isn't. -
@DaBit said in DWC 2 - Stupid #$%# popup when trying to type console cmds:
I would expect the last command entered to be on top, which it isn't.
I noticed that too when calibrating.
-
The way the PanelDue interface does it would be much better. Up and down arrows move up and down through the command history. It doesn't remember the commands between power cycles, which would be nice, but there's nothing stopping DWC from remembering them.
-
I realize that @chrishamm is busy with RRF3/Duet3 related stuff.
Is anyone proficient with DWC2 (is it javascript based?) that could explain how to just disable that "feature" (and pack it up so it can be dropped/installed on a duet?)
"I'm not saying that you are wrong - I'm just trying to fit it into my real world simulated experience."
-
might be able to swing it with tampermonkey
offending divs:
- input field
<div data-v-053bc093="" class="v-input v-text-field v-text-field--single-line v-text-field--solo v-text-field--enclosed v-text-field--placeholder v-select v-select--is-menu-active v-autocomplete v-input--hide-details v-input--is-focused theme--dark primary--text"> - command history
<div class="v-menu__content theme--dark v-autocomplete__content" style="max-height: 300px; min-width: 1674px; top: 410px; left: 312px; transform-origin: left top; z-index: 8; display: none;">
- input field
-
@garyd9 said in DWC 2 - Stupid #$%# popup when trying to type console cmds:
I realize that @chrishamm is busy with RRF3/Duet3 related stuff.
Is anyone proficient with DWC2 (is it javascript based?) that could explain how to just disable that "feature" (and pack it up so it can be dropped/installed on a duet?)
I ran into this same thing, trying to use a tablet. Overlays what you are typing, can't see.
.
-
@bearer said in DWC 2 - Stupid #$%# popup when trying to type console cmds:
might be able to swing it with tampermonkey
offending divs:
Unfortunately, I'm not at all familiar with the HTML code or how to go about modifying DWC2. Is there some way to modify a file or two on the duet SD card to "fix" this (or just get rid of it?)
Thanks
Gary -
Seemed the easiest was to remove
:items="displayedCodes"from the relevant component and rebuild it. -
@garyd9 said in DWC 2 - Stupid #$%# popup when trying to type console cmds:
I think I'm hitting ENTER on my newly entered command, I instead find that instead I sent "M1" or something else destructive.
+1. Non intuitive indeed.
Enter should send what the user typed unless the user explicitly selects one of the suggestions. Currently I type a few extra spaces to make sure it doesn't select any of the suggestions.
-
@garyd9 said in DWC 2 - Stupid #$%# popup when trying to type console cmds:
PLEASE get rid of this horrible "feature" in DWC2 that "helpfully" pops up a list of previously typed console commands every time I try to type a command.
AMEN to that
I just started using duet2eth and this is making it very hard to use...check out how terminal works on octoprint, it is ugly but works hella lot better (up/down history works ok so if you want to repeat command, up will load it into type box)
also the order of the terminal output is rather weird in latest version of dwc.. I really think you should look at how terminal for octoprint works, it's way simpler, no fancy coloring, but contrary to this fancy one on DWC it's actually useful
-
@bearer said in DWC 2 - Stupid #$%# popup when trying to type console cmds:
Seemed the easiest was to remove
:items="displayedCodes"from the relevant component and rebuild it.I removed that (from the minified file app.296c62fd.js) and it does eliminate the list of previous commands. It also seems to make it harder to overtype the one command that's in the input area. Backspace key doesn't work.
Did your re-built version do that?
-
@Danal said in DWC 2 - Stupid #$%# popup when trying to type console cmds:
Backspace key doesn't work.
Did your re-built version do that?No, can't say I noticed that, nor is there any reason it should. I'm not used to vue, and tried fiddling with it to change the enter behaviour and that had some side effects, but just removing the part that generated the list of remembered commands didn't seem to have any adverse effects.
But you'd probably want to remove the
this.addCode(codeToSend);bit further down to avoid dwc to keep adding all the successfully exectuted commands to the local storage or wherever it goes. -
Hmm, this is really a no-go and I hoped I had fixed it. I'll come up with a solution.
-
@chrishamm said in DWC 2 - Stupid #$%# popup when trying to type console cmds:
I'll come up with a solution.
would it be possible to change the enter behavior as well? Either add tab/right arrow key to populate the input field from the autocomplete list, or having to press enter twice to send past command (once to select, and once to submit)?
