Ah ! Found it.. I asked a very similar question previously:
aqObject.GetPropertyValue object does not exist after an exist check passes
AlexKaras spent some time explaining TCs caching strategy, which may be the cause ?
Hi,
Can you provide us with the source code for the getKeyboard() function and let us know what application are you working with (web, desktop, etc.) ?
Here's the code to get the keyboard. This is a desktop application.
function getKeyboard() {
var activeView = Aliases.AppName.HwndSource_Window.WindowTouchViewmodelsShellview.ShellView.Grid.ActiveItem
if (activeView.LoginView.Exists) {
return activeView.LoginView.Grid.SoftKeyboard
} else if (activeView.HomeView.Exists) {
return activeView.HomeView.Grid.SoftKeyboard
} else return null
}
I have tried a couple of other things in my findKey() function. I tried setting the shiftMode before finding the key, and it still crashes. I also tried changing the properties in my FindChild call to look like this
var key = keyboard.FindChild([propertyName, "Exists"], [character, true], 2, true)
And it still failed.
To add something else to help, here are some screenshots of the info I'm checking when I set a breakpoint on the line that fails.
As you can see, especially from the last one, the object has the property, but it doesn't actually work when calling it.
else return null
This means your function could return null. You won't be able to get the Exists property, since it's not an actual object with properties. Try rather returning Utils.CreateStubObject();
Edit:
Propertoes... As apposed to my stubby little toes :smileywink:
Based on your suggestion I added a check for that:
var keyboard = getKeyboard() if (keyboard == null) return var key = keyboard.FindChild(propertyName, character, 2, true) ...
It still crashes. I didn't think it was a problem with the keyboard anyway, as my last comment shows that the found child exists and is not null.
