I'm not a WP8 dev, but I wanted to write a little timer app for my toddler. Thing is, she shouldn't be able to turn it off by clicking 'home','back' or 'search', but by password only. Its for personal use only, so store policies/hackiness dont matter. I know it can be done on android, but how about WP8?
You could programatically block any back-button presses (though it's not compliant with windows phone store requirement), but there's no way to block start and search buttons.
Try encapsulating those buttons with some DuctTape
Does anyone know how to implement a word suggestion popup menu so that when you type letters it will open up popu menu and suggest words that you can choose from and when chosen you can continue typing much like the word suggestion in for example text messages.
This feature is already in windows phone 8 if you put the input scope for Textblock to Text but the problem is that you can't input your own words to the dictionary programatically.
I was also looking at the autocomplete for windows phone 8 toolkit but the problem there is that you can't continue typing after you have selected the word from list. Any idea how to modify that control so that you can do it ?
Thanks,
Jani
You need an AutocompleteBox, this article should help you http://developer.nokia.com/community/wiki/How_to_use_Auto_Complete_Box_in_Windows_Phone
I am making a mobile app with adobe air 3.9 and in the registration form, I wish to make email text-field have a keyboard or soft-keyboard type as email (i.e. having a button for ".com" and "#" in the soft-keyboard)and age to have numbers only.
I see some helps around but none gets me a clear idea.
Can anyone help me with a quick tutorial or a code snippet.
Thanks
Saurabh
Use NativeText, look here for the great article:
http://blogs.adobe.com/cantrell/archives/2011/09/native-text-input-with-stagetext.html
here's a tutorial
Just be aware there are two SkinClasses for TextInput and TextArea, MobileSkin and StageSkin. StageSkin can control the softkeyboard, but has scaling issues. MobileSkin can't control the softkeyborad, but doesn't have scaling issues. Follow this bug and related issues for more info about that.
I'm working on Cordova application for Windows Phone 7.
Here is my trouble. I have some fields like:
<input type="number"/>: with type number
<input type="date"/>: with type date
So, here I need digital keyboard to be shown on focus in first case and date picker in second case. On windows phone devices ordinary keyboard is displayed nevertheless the input type.
Can you suggest any suitable workarounds for my case? I assume I'll probably have to create some cordova plugin - maybe somebody experienced the same problem before and can provide me with some code snippets/links/advices.
Regards, Paul
Actually I've found beautiful Cordova plugin for DateTimePicker(and not only). Please, see https://github.com/sgrebnov/jqmobile-metro-theme.
Regards, Paul
I currently have a webpage serving up phone numbers, some of these phone numbers have extensions so I have written the HTML like this:
+44-1234-56788 / <a href="tel:+44-1234-567;ext=99">+44-1234-56799</a
When I hit this page in my Android browser and tap one of the phone numbers, it loads up in my phone dialer (UK Samsung Galaxy s2 stock) as:
+44-1234-567;ext=88
which I don't think is correct. Surely it should omit the ;ext= word.
Have I misread the RFC for implementing tel?
Seems the proper way to do it is use a comma:
+44-1234-567 ext.88
Just tested with iPhone and Android OS 2.1. Using ;ext=88 converts the ext bit into a number that is dialed with the extension (so it dials something like 35888 instead of 88).
Comment for How do I include extensions in the tel: URI?
As of June 2021 the RFC3966 ;ext= syntax still isn't implemented by Android, and it's inelegantly implemented by iOS.
Using ;ext=123 as an example:
Android: after the call connects a modal window appears asking Send the following tones? 396123 with No and Yes buttons. "Send the following tones?" is a precise technical description of what will happen if the user taps Yes, but it is probably not the best wording for the average user.
Android converts ;ext=123 into 396123 because it treats the letters the same way as if you were dialing something like 1-800-FLOWERS, and this is a broken implementation of the syntax.
iOS provides an option to the left of the Disconnect button that says Dial “ext=…”. When you tap on this "button" it will dial the extension number. This is inelegant and has bad usability because the "button" doesn't look like a button — it's just plain text — and because you can't see the extension number.
In addition, when you first tap on a phone link in iOS it presents a button at the bottom of the screen which partially rewrites the phone number into a local format, but which also preserves most of the ;ext= syntax, e.g. Call +1 (555) 555-5555;ext123. This is also inelegant, and it's ugly besides.
If you instead use just a ; which is supposed to mean "wait," as in "wait until the auto attendant message ends and then automatically dial the extension":
iOS: tapping the link displays a button stating Call +1 (555) 555-5555;123 which is slightly less ugly than the button described above.
iOs provides the same extension-dialing "button" described above except the extension number is visible, e.g. Dial “123”. It still has the other usability problems.
iOS does not automatically dial the extension after the message ends.
Android: after the call connects a modal window appears asking Send the following tones? 123 with No and Yes buttons.
Android does not automatically dial the extension after the message ends.
So for now, as of June 2021 it seems that the only way to include extensions in tel: links that will actually work is to use either ; for "wait" or , for "pause":
555-555-5555 ext. 123 — this will provide a UI component which the user can invoke to dial the extension. The usability of the UI component depends on the OS; neither are great, but Android's is arguably better.
555-555-5555 ext. 123 — this will automatically dial the extension a couple seconds after the call connects. Note: This mechanism will not work with voicemail systems that don't accept user input until the auto attendant message ends.
According to the documentation, you can add what you want like so 12345678;ext=123
See RFC 3966
In all the examples I saw, the value of ext is contained in the full number. So try including 88 in the href value:
+44-1234-56788
For those still wondering about this problem: I've found it best to use this format:
<a href="tel:+13235798328;22">
Standards at thenewcode from 3 months ago suggest using a microdata pause.
<a href="tel:+13235798328p22">
Related:
Different standards persist across different external platforms and may change the processing of URIs. Click to call
features on Google Developers docs do not specify
Example:
Office's Skype uses x to represent extension within skype.
I feel like this is kind of a cop-out answer, but if this is not implemented consistently across devices yet, probably best to just not include the extension and let people dial it by hand:
+44-1234-567 ext. 88
or
+44-1234-567 ext. 88
Better to make the user do more work than to send 1/2 your users to the wrong extension.
I don't get the answers to this question - I think the're wrong. The correct link would look like this:
+44-1234-567 ext. 88