I tried this Set Next Engine Window Position action, on release day, and couldn't get the results that I expected. I figured I'd wait until things calmed down before sending a report. Thank you for posting your results.
In addition, I couldn't get the LastWindowID token working either. I have about 7 total issues outside of main macros that I had to reconfigure to get working (i.e. - user prompts and a Citrix login screen that no longer retain focus when trying to paste into them from another macro etc.).
This will pass but I dare not inundate Peter at this time.
Speaking from a background of professional testing—without using bug tracking software, the best option is to keep one bug to one post. This makes management, questions, answers and follow ups much easy to handle.
There is a word for putting every bug into one master post. The word begins with cluster…
... and ends with duck right? Haha fair enough! Would it be beneficial to have one thread that links to the individual posts? Maybe make it easier that way to find them in the coming weeks and months?
That sounds like a good idea to me anyway. I actually looked for a "Bugs" category before my reply a few minutes ago and realized for the first time there isn't one.
A lot of posts here start with something like "Bug! I can't get this or that to work" especially from people new to the App and are actually nothing to do with Bugs. That's why I resist using the word Bug and always try to mention that whatever issue I have could be entirely my own fault and me simply not understanding how something works (it usually is...)
With these issues with KM 10 it is quite likely they are bugs as this is a fresh new version with lots of new features - which is why I put "KM 10" at the start of the post name.
@peternlewis – Have you posted a definitive “How to provide a bug report for Keyboard Maestro” topic anywhere?
It would be nice if that was codified, so we could point users to it and say “Please follow these guidelines.”
We could also post a macro that would gather any desired information about the reporting user's system. I'd think that would save everyone some time and effort.
No, because I don't dictate what people do - I don't care how you format your bug report, or where you put it as long as I see it. Any method on the Contact Us page works, or any post made here if I see it - so tagging me in will help with that.
I don't want to force folks to follow guidelines, read guidelines, or post to the correct category, which is why there is a very small number of categories.