Frequently Asked Questions

The performance benefits of “Fire only if window belongs to program”, “Match window type”, and “Match window size”

It's very cheap (in terms of cpu usage) to get the "external" properties of a window, such as its title, size, type and even the process that caused its creation. However it's relatively more costly to iterate through the contents of a window, particularly if the accessibility API has to be used.

If you enable the checks on size, type and owning process in the "Identifying the Target" page of a press/macro, then PTFB Pro can use these very fast tests to quickly eliminate a lot potential matches, saving the more rigorous matching for a much smaller number of candidates. Generally the saving from this is very small, as in scarcely measurable during one cycle (PTFB Pro does multiple cycles a second); however over the course of a day on a busy workstation with lots of windows open - it can add up.

Help Topics:


Last Updated 8 years ago


Help Topics

  • PTFB Pro