Unresponsive Bangle.js 2 prompts #4178
Replies: 1 comment
-
Posted at 2022-02-19 by HughB I experience this as well. Hitting the 'beep' ok button in the message app is a pain. on('tap') requires you to practically stab the screen to get it to work. The Would be useful for you to try these apps out and report your experience.
I would agree. If you try my UPDATE: just found the thread. I think in stopwatch touch I may check in my ontouch handler and anything greater than the width returned by g.getWidth() will clip back to g.getWidth() etc. Posted at 2022-02-21 by Subtlewolf
It appears to me that 'tap' is based on the physical movement of the watch. If that's the case Stabbing the screen is just a roundabout way to tap the front. Posted at 2022-02-21 by @gfwilliams
Yes, as @subtlewolf mentioned that's not using the touchscreen which is why you're finding it difficult :)
Do you mean you get the buzz immediately the first time? Are you on latest firmware, and have you done Posted at 2022-02-21 by Subtlewolf
Most of the time at least.
Yes and yes.
Possibly. However everything else has been responsive while prompts are reliably problematic, so at the very least they appear to be affected more. Posted at 2022-02-22 by @gfwilliams Ok, very odd - please can you give me some exact steps for something you do that makes it happen (or even a video?) and I'll see if I can reproduce here Posted at 2022-02-24 by Subtlewolf It happens very consistently at the very least with alarm app timer prompts and prompts triggered from the web IDE. Video of uploading the prompt example code and having to settle for two fish: https://youtu.be/O4mDtftum5U Posted at 2022-02-24 by @gfwilliams Thanks - but it looks like you uploaded the example code:
onto the watch. There's a Can you reproduce the problem with just a single menu shown? Or does this only happen when it's one menu and then another overwriting it right away? Posted at 2022-02-24 by Subtlewolf I should have noticed that, sorry. Good thing I do actually like fish. Posted at 2022-02-24 by @gfwilliams Well that is strange - here that works fine. Please can you try:
It should print out xy coordinates and draw a crosshair where it thinks you pressed on the screen. Maybe for some reason the XY coordinates are wrong? Posted at 2022-02-24 by Subtlewolf Well, looks like most of the issue is me my dry fingers plus some touch screen imprecision. Tapping in place can produce a minor, but distinct spread which is enough to miss repeatedly given the size of the buttons. That said, occasionally the touch event does not fire, in which case the prompt tends to not respond. Very rarely the prompt works but the touch event does not or the crosshair is drawn over a button with no response from the prompt. EDIT: notably I have not had any trouble reliably hitting, e.g., buttons in the calculator app. I don't know if there's a UX difference with full screen applications prompting me to be more precise or something else. Posted at 2022-02-24 by @gfwilliams Thanks! I've just checked on this and there was a decent size dead-zone between buttons (24px). I've just updated the firmware to remove this and also to extend the pressable area vertically a bit (it was already a little higher and lower than the buttons, but adds a little more). Hopefully that'll make things a bit more usable for you! |
Beta Was this translation helpful? Give feedback.
-
Posted at 2022-02-19 by Subtlewolf
I'm having intermittent unresponsive prompt behavior regardless of source (Messages, Alarms, custom prompts triggered from the IDE). The rightmost option is usually the worst and it can take several seconds of screen poking to finally trigger it. There is usually a buzz, which presumably indicates that the touch was registered.
The touchscreen seems to work perfectly fine with, for example, the touch timer app.
Any help or tips would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions