Squish/nativeType Function: Difference between revisions
< Squish
Jump to navigation
Jump to search
(Make it a sub-category to ensure it gets linked suitably.) |
AutoSpider (talk | contribs) (Move [[Category::Tools::Squish]] -> [[Category::Squish]]) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[Category | [[Category:Squish]] | ||
It can be the case that you need to type some text and be picked up by the application but which the receiver of the text is either unknown or very hard to predict. Think along the lines of an event filter being installed or if an object redirects events to its children. | It can be the case that you need to type some text and be picked up by the application but which the receiver of the text is either unknown or very hard to predict. Think along the lines of an event filter being installed or if an object redirects events to its children. | ||
Latest revision as of 08:46, 25 November 2017
It can be the case that you need to type some text and be picked up by the application but which the receiver of the text is either unknown or very hard to predict. Think along the lines of an event filter being installed or if an object redirects events to its children.
It's in these situations that you should always recur to the function nativeType().
It works very similarly to type() however it doesn't take an object as its target, rather, it emulates the typing a user would do to the application. This allows it to be redirected through the same paths and be picked by the proper objects.