We are making an App on libgdx, and we have a page with the login. We need the user to insert their password without the spell corrector (so, we can avoid any tipe of error).
There is a way to disable spell corrector on the phone via libgdx?
Thank you!
If you set isPasswordMode() to true on the textField there will not be any spelling correction and characters will be hidden (the latter depending on the phone settings).
Related
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
I am using dynamic text field to store score in it, I have embedded font that I am using and its only one.
But on run time while text changing one character at the left most becomes bogus/strange character, unable to figure out why its happening.
Finally I am using bitmap anti-alias for the dynamic field, it fixes the issue but text is not smooth.
If anyone had the same issue ?
You may have embedded the font, but have selected the correct character types to be embedded? i.e. if it's a score, then numerals needs to be selected like so:
(The dialog above may look slightly different in CS6, or may be somewhere else, I'm not sure; I don't use CS6)
Characters that are in the field when compiled will be embedded, and characters that aren't embedded won't render correctly.
Alternatively (instead of embedding), you can select "use device fonts" from the dropdown in the properties panel (if you have created the textfield from within Flash Pro rather than programatically), and that will fix it - literally just experienced this problem with an app I just completed and that was my fix.
If the above doesn't work, then I'm sure that it's something to do with the size of the textfield as mentioned above.
Use alternate fonts when prompted. Embed the fonts you chose, save and close your application and restart.
It solved my problem, its more likely that cs6 has this bug.
Changing CLASSIC TEXT to TLF TEXT solved the problem.
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
I have an issue in our currently running .net application. we are using autocomplete extender control associated with city textbox for city selection. Due to slow internet connection, when user uses this application with partially rendered, it is not suggesting for entered city (highlighted in red).
I have used Page_Init event for first disable the textbox, than enable it on Page_Load, but it's not working (to prevent user for enter text when the page is not loaded completely).
Is there any solution to overcome this problem?
After loaded successfully,
So you want to disable the textboxes until the page has loaded? I am not sure if it will work like you want but have you considered using jQuery to disable the textbox? For example here, here, here
this is insanely annoying problem:
AS3 full screen application based on ADOBE FLEX 4, text field. User types something in text field, and then starts clicking backspace many many times to remove what he just wrote, and for some reason, instead of removing characters from text field it tells browser to GO BACK and user navigates away. Why?! Please, please help, this is so terrible. My users are losing important unsaved this is data while using my application!
i am using safari browser
PLEASE HELP.
Wow, this is terrible, I am so irritated, it happens every single time
It is possible that the focus is lost from your text field when hitting the backspace multiple times (check if you are firing some events on the text field that may cause this), which causes the main window to take focus and trigger 'Back' on the browser.
The root of the problem is that the browser carries out keyboard shortcuts REGARDLESS of the flash app having the focus or not. From what I heard this problem does not exist on Safari's for Mac, only Safari for Windows.
I would check to see what browser you are in and then create a popup saying you this app does NOT work on Safari browser ON windows.
Scratching head*
Well maybe if HAD to solve this, I would use the ExternalInterface to interact with Safari or javascript to PREVENT the history back button from getting applied. So it won't go back to an old page. That is what I would look into.