45 replies to this topic

[Erik Slagter]

No that's not going to work.

But one option will. Something like "short" "medium" and "long".

[littlesat]

No that's not going to work.

 

-> Why? It is already working here  It automatically adjusts to the current user....

 

But one option will. Something like "short" "medium" and "long".

--> Sounds also good and easy to implement.... 1000 msec, 2000 msec, 3000 msec...

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

[Meega]

No that's not going to work.

 

-> Why? It is already working here  It automatically adjusts to the current user....

 

 

Could you explain, how this works on which user?

[littlesat]

It will measure the time between the first and second press... this by using a 250 msec timer

 

Then it calculates a next delay on the following function..

 

self.targeted_time_count = repeated_key and self.time_count < 6 and [4,4,4,5,6,8,10][self.time_count] or 12

 

minimal 1 sec delay.... max 3 seconds and when you are a slow presser it will adjust to 3 seconds or something else from a small table...

 

There is no user setting... all depends on the first (and following) presses... Each time there is an additional margin added.... minimal it stays also 1 second... max 3 seconds....

Edited by littlesat, 13 January 2016 - 16:57.

[Meega]

It will measure the time between the first and second press... this by using a 250 msec timer

 

Then it calculates a next delay on the following function..

 

self.targeted_time_count = repeated_key and self.time_count < 6 and [4,4,4,5,6,8,10][self.time_count] or 12

 

minimal 1 sec delay.... max 3 seconds and when you are a slow presser it will adjust to 3 seconds or something else from a small table...

 

There is no user setting... all depends on the first (and following) presses... Each time there is an additional margin added.... minimal it stays also 1 second... max 3 seconds....

Ok ,but that means then, that when you zap to 1-9 it always takes the longest time?

[Rob van der Does]

Even a long fixed time out will work; the 'younger people' just push 'OK' after the last digit and zapping takes place immediately.

[ims]

Even a long fixed time out will work; the 'younger people' just push 'OK' after the last digit and zapping takes place immediately.

I am never pressing OK, f.eg. ...

But one option will. Something like "short" "medium" and "long". 

It could be ok and place it to setting for RC, where is delay and repeat .

[littlesat]

I prefer no additional config... so let's see what I pushed just a few moments ago might help....

[Rob van der Does]

Even a long fixed time out will work; the 'younger people' just push 'OK' after the last digit and zapping takes place immediately.

I am never pressing OK, f.eg. ...

You don't have to, but you can. Just to speed up zapping.

Edited by Rob van der Does, 13 January 2016 - 20:23.

[ims]

 

 

Even a long fixed time out will work; the 'younger people' just push 'OK' after the last digit and zapping takes place immediately.

I am never pressing OK, f.eg. ...

 

You don't have to, but you can. Just to speed up zapping.

 

I know ... I am using zap from list

[Rob van der Does]

Hehe, me too....

[Tony il Capo]

Many of us zap from channel list, it's better, I have no idea what numbers channels have, when I use number keys I have to press OK too, because I think that it takes too much time to zap!

 

We have fast fingers - we are used to tablets, pcs, smartphones-  but for people without experience with this stuff, especially older people, they are used to older and more basic stbs, they have always pressed remote control numbers to switch channel.

 

As my experience goes, it was just a couple years ago that analog signal was shut off here. So people were used to have 4 channels (only 4 fta national channels!). They've used 1-4 keys, so it was easy for them... When digital came, receivers, both terrestrial and satellite (for national TV), were not so different, no big changes. When I started my adventure on enigma STBs, I had to put national channels in the very first bouquet, so that channel number would stay the same for my mother be able to watch tv as she was used to. If she needed to press more than one key, the box would zap to the wrong channel, because she is really slow with just finding one key.

 

Long story short, for older and inexperienced people would be nice to have longer timeouts and/or an option for being able to customize that. Channel zap is crucial for everybody, they may have no idea how the stb works, but if they can switch channels, it's all good!

Edited by Tony il Capo, 13 January 2016 - 22:53.

[Dimitrij]

Ver 1.0-rc13
 Extended NumberZap Plugin for Enigma2

 

-Setting milliseconds first pressing key
-Setting number of digits
-Support Full-HD skin
-fix picon for alternative channels

Edited by Dimitrij, 14 January 2016 - 00:10.

[Rob van der Does]

So again a plugin instead of a configuration setting
PLi relies on far too many plugins to make the image workable.

Edited by Rob van der Does, 14 January 2016 - 06:55.

[littlesat]

Why make comfigs if you can do it automatically....

[Rob van der Does]

What will the 'automated lag' be when only one digit is required to zap? So when the active fav-list has max 9 services?

[littlesat]

You can make 1000 configs.... but with 1000 configs also nobody can get it optimized... and you create more chaos and you need more spaghetti code to get all the configs supported...

 

I think it is fine as it is now.... Nobody needs to config... To speedup you still have the OK button.... And when you press buttons quickly, you also get with less digits quick response...  You can always type more digits when you want (not limited to max digits by a setting).... No configs required... Less complicated.... The slow presser's issue from this topic is addressed.... Most people happy...

 

I still convinced some "other" images want to put as many configs in their image as possible... I think at least this is not a good approach... You must try to avoid configs as we have already in our image(s).... But I realize sometimes this requires compromises....

Edited by littlesat, 14 January 2016 - 12:02.

[Tony il Capo]

You can make 1000 configs.... but with 1000 configs also nobody can get it optimized... and you create more chaos and you need more spaghetti code to get all the configs supported...

 

I think it is fine as it is now.... Nobody needs to config... To speedup you still have the OK button.... And when you press buttons quickly, you also get with less digits quick response...  You can always type more digits when you want (not limited to max digits by a setting).... No configs required... Less complicated.... The slow presser's issue from this topic is addressed.... Most people happy...

 

I still convinced some "other" images want to put as many configs in their image as possible... I think at least this is not a good approach... You must try to avoid configs as we have already in our image(s).... But I realize sometimes this requires compromises....

You created the fix, so you're happy with it because it does not really matters to you.

 

When you guys argue so much to not install any plugins and then put out of configs a simple option to configure it to user taste, I think it's really bad.

Like Rob says, going like this, more and more plugins will be needed.

[Dimitrij]

There is a solution.
Just use the plugin.
I do not see any problems .

[Rob van der Does]

@ Littlesat: again, how is your 'automated delay' going to work for a one-digit channel zap? The 'slow people' we're talking about here are not being helped by the option to use the OK-button to speed things up.