Premise Input buttons

[etc6849]

123, if you're planning on a new release there were a few minibrowser issues I had in this thread: http://cocoontech.co...es/page__st__30

The biggest problems I ran into were two white screen issues; one being related to a refresh issue and the other being related to the clientsession timeout.

ClientSession Timeout:
I have no idea while your Audrey's are not having this issue?

This solution below was a non-elegant work around; feel free to chime in as I'd love to have a real fix for this as this issue limits theme functionality to single theme.
http://cocoontech.co...post__p__156689

Refresh issue fix:
http://cocoontech.co...post__p__157205

 

[123]

The mbSecuritySystem buttons never actually call the doKeypadCancel functions (I think?!?):

Right you are! I saw it listed in header and overlooked to consider it was there for use by zWaveLock and GarageDoorOpener but not by SecuritySystem.

BTW, in SecuritySystem's mbRenderPage, on line 75, there is a reference to a variable that is never initialized: sCellEnd

 

[123]

123, if you're planning on a new release there were a few minibrowser issues I had in this thread: http://cocoontech.co...es/page__st__30

The biggest problems I ran into were two white screen issues; one being related to a refresh issue and the other being related to the clientsession timeout.

ClientSession Timeout:
I have no idea while your Audrey's are not having this issue?

This solution below was a non-elegant work around; feel free to chime in as I'd love to have a real fix for this as this issue limits theme functionality to single theme.
http://cocoontech.co...post__p__156689

Refresh issue fix:
http://cocoontech.co...post__p__157205

Whew! You folks were busy while I was playing in the Adirondacks last Spring! Thanks for resolving the refresh issue. As for the session timeout, my Audreys are never connected to the server for more than a few minutes so I've never experienced the problem. I'll see what I can do but no promises because I rarely use MiniBrowser.

I've created a version of SecuritySystem that does not rely on JavaScript. I've confirmed that the Voyager browser in a 3COM Audrey does not know how to handle the most basic usage including "onclick=some JavaScript function". That rules out using SecuritySystem in the version of MiniBrowser you created.

1. The version I've created stores the digits in a property called PassCode. PassCode serves as a temporary buffer for the digits entered by the end-user.
2. Pressing a digit-key, on the keypad, appends the digit to PassCode.
3. PassCode is displayed onscreen but the numbers are masked (i.e. an HTML INPUT whose type is 'password').
4. When a digit-key is pressed, it restarts a ten second watchdog timer.
5. If the watchdog timer is allowed to expire, it purges PassCode. This ensure PassCode is never stored for more than ten seconds.
6. Pressing the Enter key copies the PassCode to the DisarmCode field (if greater than 3 characters in length). This behviour is consistent with how the SecuritySystem keypad works in AutomationBrowser.
7. Pressing Stay, Arm, or the Exit key will confirm if DisarmCode is populated, execute the chosen function, then purge PassCode and DisarmCode.

It works like a charm on my Javascript-challenged Audrey (and on my PC, of course). The only glitch, and it's a minor one, can occur while entering the passcode. If you wait more than ten seconds between key-presses, the passcode property is purged (by design) but the onscreen display of passcode is not purged (no way to do that without JavaScript). You have to refresh the screen to see that the passcode field was erased ... and that occurs after you press a key (like pressing another digit-key).



I noticed you made several corrections elsewhere in MiniBrowser and I'll probably pick your brains before I post an updated version of MiniBrowser.

 

[chucklyons]

I'll want to lift your keyboard buffering piece for the channel/tuner frequency functions in my device modules - I currently use 'this.setvalue, "channel", "0"' to clear the previous channel and enter a new channel (uses same philosophy as the AB version of channel then number entry)

I also have some changes to the MB you should incorporate w/ a new release...