Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No Answer seen in Yes/No option #54

Closed
Reiskakivi opened this issue Feb 23, 2013 · 6 comments

Comments

Projects
None yet
3 participants
@Reiskakivi
Copy link

commented Feb 23, 2013

Answer comes only after waiting 30sec. Is there chance to see answer as soon as it given.
And if no answer it gives automatically Yes!

@jbleyel

This comment has been minimized.

Copy link
Contributor

commented Feb 26, 2013

i have no idea why?!?
i have increased the timeout but the answer is YES if no key pressed

@Edgarvh

This comment has been minimized.

Copy link

commented Feb 26, 2013

Yes, the countdown goes to zero and then you get an answer and indeed in case no answer is given you get 'yes' though. Better to get the answer directly, before the zero of countdown. I thought old webif did the same. Maybe better to say 'no answer given within time'

I don't know if it's possible to make a funny add on that: let it be possible to type an answer directly on your television. Like a small chat.

@jbleyel

This comment has been minimized.

Copy link
Contributor

commented Feb 26, 2013

I think the problem is inside the javascript.
When i call the messageanswer api request in a separate browser then i get the right answer

@Edgarvh

This comment has been minimized.

Copy link

commented Feb 26, 2013

Hmm ok. Same Javascript as the other interface?;) My girlfriend always gave the answer yes while she were asleep, I heard later on. Happened in the time before Openwebif exists.

@jbleyel

This comment has been minimized.

Copy link
Contributor

commented Feb 26, 2013

I have analysed the problem and i have found the "bug" in Screens/MessageBox.py .
If no key pressed the default key will pressed after timeout.
I have also checked the webinterface plugin and there is no messagetype yes/no.
The only chance to fix this is to rewrite the MessageBox function in enigma2.

Sorry for the bad news.

@jbleyel

This comment has been minimized.

Copy link
Contributor

commented Mar 8, 2013

Please check this

and close the issue if it works

cab8874

@jbleyel jbleyel closed this May 11, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.