Roku Developer Program

[EnTerr]

"Komag" wrote:
I hacked a way to avoid it - simply detect when * is pressed (rather, when it's released - id 110), and then do some other benign button press (I'm using "backspace", id 11, 111) to break the pattern, so it's impossible to get four * in a row!

Congrats on thinking outside the box, that is a clever hack!

I am not much of a fan of hacks, since they tend to be fragile. I.e. the Co may unwillingly "find a way" around what you are doing in next version. But an improvement suggestion: use "http://localhost:8060" instead of specific IP (that did not work in 1xxx/2xxx players but they are out of the picture now) - not only will that shorten your code but won't break if there is no network connection and GetIPAddrs() returns squat.

[Komag]

This seems to be working:

FUNCTION doBackspace()
 xfer = CreateObject("roURLTransfer")
 url = "http://localhost:8060/keypress/Backspace"
 xfer.SetUrl(url)
 xfer.PostFromString("")
END FUNCTION

Thanks for the tip

[ljunkie]

It looks like the manifest has an additional option that may help, unless it does the same thing as roAppManager.SetAutomaticGuideEnabled.

automatic_audio_guide_disabled=1

[belltown]

"ljunkie" wrote:
It looks like the manifest has an additional option that may help, unless it does the same thing as roAppManager.SetAutomaticGuideEnabled.

automatic_audio_guide_disabled=1

That completely eluded me. I overlooked the note at the top of the officlal-but-now-deprecated manifest file documentation, https://sdkdocs.roku.com/display/sdkdoc/Manifest+File that referenced the "work in progress" GitHub docs. They might as well just remove the outdated documentation completely, leaving just the link to the updated documentation if they're not going to keep the sdkdocs.roku.com docs updated.

[EnTerr]

"belltown" wrote:
That completely eluded me. I overlooked the note at the top of the officlal-but-now-deprecated manifest file documentation, https://sdkdocs.roku.com/display/sdkdoc/Manifest+File that referenced the "work in progress" GitHub docs. They might as well just remove the outdated documentation completely, leaving just the link to the updated documentation if they're not going to keep the sdkdocs.roku.com docs updated.

I don't like that schism. There should be a Single Source of Truth on the platform^. What's the benefit of writing docs on GitHub vs Confluence Wiki? I am not persuaded GH has advantage. Examples - yes, definitely better to have them on GH - but pre-existing documentation? Has the doco writer run out of things to do but will waste effort to convert from working format A to another format B?!

(^) fineprint mumble: bugs and omissions excluded.

[Komag]

"ljunkie" wrote:
It looks like the manifest has an additional option that may help, unless it does the same thing as roAppManager.SetAutomaticGuideEnabled.

automatic_audio_guide_disabled=1

I just tried it, doesn't stop from turning on and off the audio guide in-game, so I'm still going to use my hack. I'm guessing it turns off any "guidance" while in the channel, but doesn't turn off the person's ability to enable/disable the audio guide overall.

[Romans_I_XVI]

Thanks for this hack Komag! I've implemented it in to the core of my framework 😛
https://github.com/Romans-I-XVI/Roku-ga ... 94b4eb94a0

One thing to note. I noticed if you post the backspace event after the info button press (code 10) you might receive a double button press for info if you keep holding it. Along with that I was also having issues with the info button release event not happening as it should. The easy solution was to just send the backspace event after the release of the info button, personally I'm doing it only if the button had been pressed 3 times in a row.

Thanks again, this was a very annoying issue, I always had to consider where/when/if I want to use the info button just because if somebody presses it multiple times they'll accidentally turn on the audio guide (which serves no purpose in game).

[RokuBen]

The CVAA law that mandated audio guide (https://www.fcc.gov/consumers/guides/21 ... y-act-cvaa) says there always has to be a key shortcut to enable it by default.  We provide a setting to disable the shortcut, but alas, we have to default to that being enabled to be compliant.

[Romans_I_XVI]

Ah, thank you for the additional info RokuBen

[pammie0888]

Tried all your directions to turn off audio guide. NOTHING shuts her up. Please don't give me code type talk, I'm technologically impaired, but not visually impaired. HELP!