djs wrote:While I would love to see this working, keep in mind, one of the great things about Macro Scheduler is the flexibility of how things are done.
If gettextpos isn't working, use image recognition, with the new image recognition stuff, its pretty bullet proof and is a reasonable substitute. Just grab a quick screen image of the text and then let Macro Scheduler find the image.
Yes, I need this to work as well, but as a consultant, I get paid to find solutions, not problems. I'm sure most of you are the same way.
Dan
I appreciate your perspective, Dan, and I agree on principle that consultants (or in my case, internal support engineers) should always seek solutions rather than only complaining about problems. Unfortunately, with respect to your recommendation, we did try using image recognition, and while it was functional, it is simply too slow for the purpose of this macro (a macro with the purpose of speeding data entry, so image processing delays are a significant issue). In addition, while image recognition is a possible substitute for text recognition, there is currently no reasonable replacement for GetWindowText (FWIW, GetWindowTextEx doesn't work either).
In other words, in this case, the problem is significant enough to create an impasse. And while I am thrilled with Marcus' product overall, since this particular issue has remained unresolved now for over a year without any update (until I resurfaced it), I would say that it is very appropriate that the user community (especially those of us who have paid a significant license fee for use of this product) takes the time to draw attention to real issues such as this and do everything we can to help ensure that it is resolved appropriately.
On that note, I do want to thank Marcus for responding so quickly when I resurfaced this issue. Please do keep us posted as you continue to remind your library developer, so we don't think you have forgotten about us.