45 replies to this topic

[odokrim]

The keypress timeout is to short when tye a 3 digit channel number.

I cant find any settings in image to increase time.

[littlesat]

here no problem with three digits.... and we should avoid too much configs...

[Pr2]

On which box (brand and model)?  

I have no problem neither on mine.

[Dimitrij]

The keypress timeout is to short when tye a 3 digit channel number.

I cant find any settings in image to increase time.

use plugin Systemplugin Extnumberzap

Edited by Dimitrij, 12 January 2016 - 14:05.

[odokrim]

Box: Vu+ zero

After second number Box is switching to channel. You have less than 1 second time to enter 3rd number in channel selection.

[littlesat]

That was intended..... and requested in the far past to reduce that time...

 

actually the time on the first is 3 seconds... and every following digit is exactly one second (and not less than once second).... When you press blue (going to the first userbouquet) it is again 3 seconds,

 

When it is less than one seconds as you reported something is wrong on your box (plugin installed? modified InfoBarGenerics? Stolen NumberZap class by a plugin???)

 

About this timing schedule, which we have it there for years...

Edited by littlesat, 12 January 2016 - 16:54.

[ims]

here no problem with three digits.... and we should avoid too much configs...

It is not wrong idea - make it configurable (optionaly increase time for next digits  ... Standard / Extended time). My old dad's hands are able press channels with 2 digits only. I must place all wanted channels as double-digit only and it is big limit.

 

I think, exist more "less useful" configs but this could be useful for old or handicap people... there are not all young and health people on the world

 

.

[littlesat]

OMG... another setting and we already have that much..... Then I prefer to make a new fixed value.... Is 1.5 sec better?

[arn354]

We had allready implemented - take it or close it


https://github.com/O...nigma2/pull/158


Add option to configure zap delay - per default config options are not visible (level=2) and default values as they were are taken.


Add option to increase digits to 5 (more then 9999 services) - per default config option is not visible (level=2) and default value as it was are taken.

Edited by arn354, 13 January 2016 - 10:18.

[ims]

OMG... another setting and we already have that much..... Then I prefer to make a new fixed value.... Is 1.5 sec better?

 I cannot tell you, if 1,5s will be ok and if it will be ok after several months too ... it has progress :-(

I am affraid -  2-3sec.

 

May be, add standard value into settings and solve it extra plugin ?

Edited by ims, 13 January 2016 - 10:34.

[WanWizard]

I agree with you, you need to take older people into account. My mum has never been able to use it, it takes her 2 seconds minimum to find a number key.

 

And I think it is mainly older people with a limited amount of channels they watch, and with a experience of using a standard analog TV etched in their memory, that use this. I have hunderds of channels I watch, I haven't got a clue what numbers they have, I always zap via the list.

[arn354]

exactly for older/slower people we implemented those options. Some people need 1-2 seconds to find the next number to press

[littlesat]

This was in here for years and now somebody is arguing... wierd that after years this suddenly get a topic...???

 

Making it longer is also not comfortable.... that is my meaning... adding a setting is also something we should think about...

 

We can consider to use 3 seconds in any case... let's see of somebody noticed it... We still have the OK button available to speed thinks up!

[WanWizard]

"Why does your car have power steering? Not needed, people drove for 50 years without it."

 

If you have this mentality, innovation will seize to exist. In case of my mum, she simply takes sometimes a very frustrating few minutes to change a channel, and most of the time, asks my dad to do it for her. With a longer timeout she will not be dependent on him (for watching TV) anymore.

 

I'm pretty sure this isn't the first time this is mentioned, but without an issue tracker to record and follow up outstanding issues, things reported on the forum will be forgotten the next day, unless someone actually picks it up directly.

[arn354]

I proposed a pull-request we use for months. Usually with normal level of config.usage.setup_level people do not see those "new" settings at all. Only if you change config.usage.setup_level to 2 you will see those those additional menu entries. The defaults are as they are hardcoded right now - so nothing changes if someone does not intentionally changes those settings.

Edited by arn354, 13 January 2016 - 11:18.

[ims]

and is it problem add it into config for RCs ? There are 2 options items only...

[Dimitrij]

please apply this https://github.com/a...9c2bea5039a1e92

[littlesat]

That patch suggestion is not acceptable.... Too many (4) configs are added.... Sorry I'm thinking like Steve Jobs here...

I think we should only use 3 sec timeout.... And to make it faster the user can press the OK button...then we do not need to add 4 configs... And keep the code clean...

 

Just a suggestion...

 

When we do something I would prefer to do all with one config.....

 

Numberzap timeout... 1,2,3 seconds

 

Then first number = numberzap timeout + 2 extra seconds.... other like the config said...

Edited by littlesat, 13 January 2016 - 13:56.

[arn354]

regarding numberzap delay it's 3 config options - yes, might be optimizable, but i am not the professional 

The fourth config option is just to enhance the amount of digits (if more services then 9999).

Edited by arn354, 13 January 2016 - 14:14.

[littlesat]

One option is already too much....!!!

But I'm thinking about an auto config option No configs required at all.... Just measure the time between the first and second press and timeout this time + an additional time of half a sec.... No config needed and slow pressers get automatically more time...

Edited by littlesat, 13 January 2016 - 15:04.