[Blink] Latest Blink breaks pound DTMF key (#) - sends '3' instead of '#', which is Shift-3
bartvolgers at gmail.com
Thu Apr 10 01:23:59 CEST 2014
On 10 apr 2014, at 0:07, Raymond Savoie wrote:
> On Wed, Apr 9, 2014 at 7:10 AM, Bart Volgers <bartvolgers at gmail.com> wrote:
> Plaatsen om een kat te zoeken:
> Achter de boeken op de boekenplank.
> In iedere kast die op een te klein kiertje staat.
> Boven op iets heel hoogs.
> Onder iets dat te laag is om onder te kruipen.
> In de piano.
> I didn't think to look in the piano!
Really it should be the first place to look ;-)
> > Over my cold dead body ;-)
> Seriously. Think NOT adding keypad is the right thing to do. Having a keypad and need to click the keys with your mouse…. That's a really awkward user experience. Can't figure out why people want that. Just press the Real numeric keys on your keyboard, even using the upper numeric row on my laptop is a good user expressions. Or buy one of these nice numeric keypad with USB. Plug it in and start dialing :-)
> Wow - such vitriol directed against a little virtual keypad! Here are some reasons why it such a keypad can be useful, aside from the current situation where the # key doesn't work:
It's not "just a little virtual keypad"
One of the strong arguments against a keypad can be boiled down to: "Feature creep" See e.g. http://en.wikipedia.org/wiki/Feature_creep
Feature creep never makes a strong product.
> 1) As a novice Blink user, I was looking for the keypad function and couldn't find it. The GUI is quite simple, which is a plus, but it was not immediately clear to me that I could simply type the numbers on the keyboard. Having a virtual keypad that could pop up on demand does not preclude the ability to capture keyboard input, and I suspect other novice Blink users may appreciate having the option as well.
> 2) The virtual keypad could have the standardized letter 'mappings' visible on each key. (Please refer to http://www.quickiwiki.com/en/Telephone_keypad) In North America many institutions will make use of this mapping. For example, my brokerage house (Fidelity) requires me to type in an alphanumeric password using the DTMF keypad. The letters ABC map to 2, DEF to 3, etc..
I am really perplex that they use a system like this…. It's totally un-usefull to make up an complex password if it's just translated back to an numeric sequence. It can also give an un-save perception of safety, as your password is just a sequence of numbers. Also it is transmitted over an non encrypted connection in numeric DTMF code. I think I wouldn't rely on that and move to a brokerage house one with a better understanding of safety. If you want to continue to use this with Blink you need to make a lookup table to enter them a digits . Wanting a keypad added to support an un-save and outdate password scheme will not make a strong argument.
> Regardless, of the above it doesn't sound like I'll be able to convince anybody into adding a virtual keypad. Apparently the thought has struck a nerve or something! Haha!
Yes it reminds me on all the bloated programs from the past century. I am happy a lot of developers moved past that point and make agile programs
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Blink