roCodeRegistrationScreen isKeyPressed() work around?

No event is generated for any key press on roCodeRegistrationScreen as far as I know. So probably you wouldn't be able to do it using * button. But I have seen other channels to add a button for demo (I think you are talking about displaying demo content to user instead of self testing the application?) on roCodeRegistrationScreen (Vevo does so as far as I remember). For example you can add two buttons on roCodeRegistrationScreen titled "Get a new code" and 2nd "Continue without logging in" and if user selects 2nd button you can carry on to displaying demo content. As for these button isButtonPressed() will be fired.

Have you tried listening for the isButtonInfo() event? Not sure if that works on the roCodeRegistrationScreen or not, but some screens raise it instead of isRemoteKeyPressed() for the * button.

"scorpiontahir02" wrote:
No event is generated for any key press on roCodeRegistrationScreen as far as I know. So probably you wouldn't be able to do it using * button. But I have seen other channels to add a button for demo (I think you are talking about displaying demo content to user instead of self testing the application?) on roCodeRegistrationScreen (Vevo does so as far as I remember). For example you can add two buttons on roCodeRegistrationScreen titled "Get a new code" and 2nd "Continue without logging in" and if user selects 2nd button you can carry on to displaying demo content. As for these button isButtonPressed() will be fired.

I have implemented that solution, however my client wants a method that doesn't impact on visual layout.

I have also implemented a solution that progresses to the next screen based on the number of times the user has re-generated a code i.e. pressed a "Generate a new code" button. This doesn't impact on the visual layout, but my client wants to associate this demo transition with A or B remote key press. I know this sounds simple, and should be simple, but the limitation of the template screens introduces complexity.

roImageCanvas might be the way to go then.

"tim.a.lacey" wrote:


I have implemented that solution, however my client wants a method that doesn't impact on visual layout.

I have also implemented a solution that progresses to the next screen based on the number of times the user has re-generated a code i.e. pressed a "Generate a new code" button. This doesn't impact on the visual layout, but my client wants to associate this demo transition with A or B remote key press. I know this sounds simple, and should be simple, but the limitation of the template screens introduces complexity.

Best choice for you is to make your client understand limited functionality of roCodeRegistrationScreen and add a button on screen for demo purpose like other well known channels do. Other choice is, you will have to design a custom screen yourself that looks like roCodeRegistrationScreen (in look or functionality or both) but does additionally what you want it to do (demo with * button) using either roImageCanvas or roScreen. But It will take some effort and time and you will have to understand roImageCanvas or roScreen a little bit if you have not used them in past.

"TheEndless" wrote:
Have you tried listening for the isButtonInfo() event? Not sure if that works on the roCodeRegistrationScreen or not, but some screens raise it instead of isRemoteKeyPressed() for the * button.

roCodeRegistrationScreen does not trigger any event on any button press (of course it will trigger for OK button when some on screen button is selected but not for any other button), not even for UP and Down buttons when pressed for navigation between on screen buttons as far as I have tested it. So wait() is never interrupted even not with Invalid msg.