restriction-card icon indicating copy to clipboard operation
restriction-card copied to clipboard

Duration reached feedback missing in case of hold action

Open schnillerman opened this issue 10 months ago • 7 comments

Is your feature request related to a problem? Please describe. If duration for hold action is set to a value, one can never know if the duration is reached and the lock is open. I usually end up trying several times before the row gets unlocked.

Describe the solution you'd like If a duration for unlocking an, e.g., row with a toggle is defined, a vibration or color change of the lock or both as soon as the duration is reached would be nice.

Describe alternatives you've considered N/A

Additional context Example script:

type: entities
title: Macchina Caffè
entities:
  - type: custom:restriction-card
    row: true
    duration: 5
    action: hold
    card:
      entity: switch.macchina_caffe
    state_color: true
  - entity: script.sveglia_macchina_caffe

schnillerman avatar Mar 05 '25 12:03 schnillerman

I am not getting, what is the issue here? The lock comes back after 5 seconds.

Image

ildar170975 avatar Mar 05 '25 13:03 ildar170975

Oh I'm sorry I realize that my explanations might've been ambiguous.

I understand that duration refers to the time that one needs to tap (press down) on the row in order to unlock. After unlocking, the lock then seems to re-activate after ca. 2 seconds (not 5 seconds like in my example for the duration value, anyways).

So what I end up doing is I'm counting the time that I press down on the row to unlock it since there is no way of telling if it's unlocked until you release mouse (or lift finger on mobile). The lock only unlocks after release of the mouse / finger.

This is the reason why I was suggesting that a feedback be implemented that the pressing down on the row has unlocked before releasing too early.

Does this make sense now? It's not a biggie, but playing around for the first few times made me struggle just a tiny bit in figuring out if I had tapped / pressed down long enough to unlock the row.

By the way, this restricted-card is AWESOME !!!

schnillerman avatar Mar 05 '25 18:03 schnillerman

I understand that duration refers to the time that one needs to tap (press down) on the row in order to unlock. After unlocking, the lock then seems to re-activate after ca. 2 seconds (not 5 seconds like in my example for the duration value, anyways).

Correct.

The lock only unlocks after release of the mouse / finger.

That is right! This is when a particular event is sent.

This is the reason why I was suggesting that a feedback be implemented that the pressing down on the row has unlocked before releasing too early.

Sorry, unclear. Please elaborate.

ildar170975 avatar Mar 05 '25 19:03 ildar170975

If I press down I don't know when to release my finger (whether I've pressed long enough to unlock). The only way is to count the seconds and find out after lifting finger.

Compare it maybe to the iPhone torch icon on lock screen. You have to press long and it vibrates during pressing to signal that it's been unlocked so you know you can stop pressing.

schnillerman avatar Mar 05 '25 20:03 schnillerman

I am curious why would you need this "duration of press-down" counter? If you pressed & immediately released - the card will not be unlocked & you will still see the lock icon. None of stock cards tells a user "this is a proper hold, now you can release".

ildar170975 avatar Mar 05 '25 20:03 ildar170975

Yes, I agree. As said, I found myself trying several times but not pressing long enough. If the duration is 5 seconds, it's just a little tedious if you end up trying several times.

But I can see that my idea might be a little over the top.

schnillerman avatar Mar 05 '25 21:03 schnillerman

trying several times but not pressing long enough

Have you experienced troubles with a touchscreen device? Asking because users are usually complaining about difficulties with "hold" with touchscreens.

But I can see that my idea might be a little over the top.

I would say that it is more related to accessibility & a11y... Besides mentioned difficulties with touchscreens, some users experience personal issues with "hold".

ildar170975 avatar Mar 05 '25 21:03 ildar170975