I'm using the PhoneTextBox from the Windows Phone Toolkit with InputScope="Text" to get autocorrect and text suggestions. While typing in the keyboard the text suggestions appears above the keyboard and I choose one of them. Immediately after the suggestion is taken the cursor of the TextBox resets to the start position. So if I continue typing then the new text is inserted at the beginning of the TextBox.
Here's an example: After choosing the text suggestion "Tests" the cursor begin of line.
EDIT:
The issue is caused by an calling of BindingExpression.UpdateSource() within the TextChanged event handler. I can't find a workaround so I created an issue: https://phone.codeplex.com/workitem/11766
I'm using a Windows 8 phone with the regular Phone 8.0 SDK.
<toolkit:PhoneTextBox InputScope="Text" BorderThickness="0,0,0,3" Background="{x:Null}" Foreground="White"/>
It works fine on my end. I would check if there are any attached events (maybe TextChanged) that would cause the cursor to reset.
Related
The MarkupsCore extension automatically creates a text area when you click that you enter text into. Now, I automatically insert text into this text area, but cannot find out how to close it programatically. After going through the source a little bit, it seemed like the text area was a little bit custom as I saw there were some custom implementations of the backspace button, etc. So, I assumed there was a different event.
It seems to happen when you focus out of the element, but that event didn't seem to do it either. In version 3 (or maybe it was earlier, I can't remember), you used to press the enter key. Now you just focus out.
So, what event needs to be fired in order to tell the extension to close the text area and create the markup?
Try the following...
Using the 'markupscore' object, send a 'mouse down' event with 'target:null' like this...
markupscoreExt = viewer.getExtension("Autodesk.Viewing.MarkupsCore")
markupscoreExt.onMouseDown({target:null})
As you are in the middle of typing some text, you can trigger the mouse down event to complete the text.
Let me know if that helps.
Cheers
Michael
Please help!
Recently (probably with version 66), Chrome began displaying its autocomplete-suggestion drop-down on the initial mouse click into a search field instead of waiting until a character is typed.
How do I make Chrome go back to not displaying suggestions until I begin typing?
I have always made use of Chrome's suggestions drop-down for search fields, but I don't want or need to see a list of random suggestions just because I've clicked into an input field. I only want to see suggestions that match what I start to type (which is how it always worked until recently).
I tried disabling the "Single-click autofill" flag and even the "Show autofill predictions" flag as well, but these flags don't seem to affect the situation. Perhaps the term autofill in these flags doesn't refer to the same thing?
If anyone can help me with this, I'll be your best friend forever and ever!
Thanks for reading this.
I was having the same issue recently with a datepicker input. To get around it, I wrapped my inputs in a form and set autocomplete="off" in my form tag, as Chrome only recognizes that property for forms and not individual inputs. I added a keyup event so that if the input has text in it, autocomplete is re-enabled:
if (val.length > 0) {
$('#myForm').attr('autocomplete', 'on');
} else {
$('#myForm').attr('autocomplete', 'off');
}
You can also add an onBlur event to disable autocomplete suggestions each time you leave an input.
In one of my PCs when I use inspect tool in chrome, I can't select some part of a property or a value, so I have to retype all the value again. As many times as I click on the selected text, the caret doesn't go to the place I need and the selected text doesn't deselect.
the following picture shows what I want and what happens.
There is no problem in another PC.
Both are windows 10 64bit and google chrome 62.
Try holding shift or control while clicking. Haven't tried it, but it may work. My guess is that it's simply a UX workflow that DevTools doesn't handle well.
When typing a query into MySQL Workbench, the autocomplete suggestion popup is so slow. After typing a couple letters of a column or table name, I have to pause for about a second or more for the suggestion box to popup.
Is there anyway to make the suggestion box appear immediately as I'm typing rather than wait for a pause?
This is on purpose to avoid that the popup comes up constantly while you are typing (the delay is 500ms atm, hard coded). However, by using the hot key you can always trigger code completion immediately (on OSX this is command + esc, otherwise control + space bar).
Yes, It works
If you have each schema open (dropped down) in the Navigator, the autocomplete will work.
Thanks
for more information refer to this link
MySQL bugs
Thanks
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.