OMG... Who does use it for just one digit?... 
Slow zappers are helped... the initial timeout is 3 sec as it always was....
Edited by littlesat, 14 January 2016 - 14:02.
Channel number zap timeout
Started by odokrim, 12 Jan 2016 11:59
45 replies to this topic
Re: Channel number zap timeout #41
-
- PLi® Core member
- 57,120 posts
+698
Excellent
Posted 14 January 2016 - 13:59
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: Channel number zap timeout #42
-
- Senior Member
- 7,766 posts
+184
Excellent
Posted 14 January 2016 - 14:40
OMG..... you haven't read? As I said: people with max 9 services in a bouquet.
Not very strange: I have several bouquets with only a few services.
Re: Channel number zap timeout #43
-
- PLi® Core member
- 57,120 posts
+698
Excellent
Posted 14 January 2016 - 15:58
You are a genius to always pick extreme situations.... Then use OK... no issue at all!!!
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: Channel number zap timeout #44
-
- Senior Member
- 7,766 posts
+184
Excellent
Posted 14 January 2016 - 16:04
Hehe, now the circle is round again. 'OK' is always fine, but the longer duration was meant for the 'elderly people'. they are not going to look for an extra button.
So for the 3rd time now: how is your automated delay going to react when only a one digit number is used?
Re: Channel number zap timeout #45
-
- PLi® Core member
- 57,120 posts
+698
Excellent
Posted 14 January 2016 - 16:09
one digit = 3 sec timeout....
2 digits is timeout between 1st and 2nd digit + a bit or more extra...
I would say play with it and look at the current code....
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: Channel number zap timeout #46
-
- Member
- 16 posts
0
Neutral
Posted 16 January 2016 - 12:25
Thank you for your quick and helpful support !
8 user(s) are reading this topic
0 members, 8 guests, 0 anonymous users
