UI/UX Brainstorming

Software
63

It would seem there’s been a rollback of the double-tap or hold 4 seconds to set XY home (which was never very good on my iPad; it took an indeterminate number of touches to successfully double-tap, and every time I tried to hold, it selected the text on the button), and now (v0.88), I can’t set it at all from my iPad. Works from my computer, but sometimes the iPad is the least cumbersome option.

Any thoughts on if/when that might have a resolution?

Mahalo,

1 Like
64

I did that originally so I could have a look again. A lot of the event handling has been cleaned up, but that’s just moving things from one place (the HTML) to another (in the JS) where it belongs

3 Likes
65

I’m pretty sure that specific functionality I removed, because it would never work on most touch devices. Holding for that long brings up context menus, selects text, etc.

2 Likes
66

Is there a way that we can make it work on touch devices? Maybe double touch?

1 Like
67

Instead of relying on a number of taps/clicks on the same target, why not just open a confirmation dialog:

if ( window.confirm("Are you sure you want to zero the Z axis") ){
     zeroZAxis();
} else {
   // do nothing
}

Really basic proof of concept https://codepen.io/tryon/pen/XJWbRqx

2 Likes
68

I think that we had that initially, but it was annoying to get a popup. Someone pointed out that the REAL right solution is probably to have an undo option so we don’t have to stress so much about making it hard to click accidentally

1 Like
69

That’s the code I put in there - specifically an actual double click handler.

In tablet.js there’s this block of event handler declarations:

    // Buttons - Fourth Row
    id("tablettab_set_z_home").addEventListener("mousedown", tabletSetZHomeMDown);
    id("tablettab_set_z_home").addEventListener("mouseup", tabletSetZHomeMUp);
    id("tablettab_move_to_xy_home").addEventListener("click", moveHome);
    id("tablettab_toggle_units").addEventListener("click", toggleUnits);
    id("tablettab_set_xy_home").addEventListener("mousedown", setHomeClickDown);
    id("tablettab_set_xy_home").addEventListener("mouseup", setHomeClickUp);
    id("tablettab_set_xy_home").addEventListener("dblclick", setXYHome);

The last three all relate to that one button. And you can see the dblclick event handler registered there.

In many OSes there are specific settings for double click/tap, for both the delay between the individual clicks/taps and for the spatial tolerance between the clicks/taps.

And they sometimes tweak these without asking between OS versions.

Aaaand they sometimes don’t have a place in the OS settings to access these values and change them

1 Like