I didn't have this issue before upgrading to version 10. Is there a setting I've missed that will force evaluation by default?
tiffle
February 27, 2022, 7:11pm
2
It’s to do with the Evaluate Condition Results setting in the KM View menu.
For a bit more info, see this:
Up until recently, I've been experiencing severe slow-downs and even prolonged non-responsiveness of the KM editor. This was especially noticeable after just running the KM app.
What I found was the following setting was the cause - Evaluate Condition Results. Here is how it looked on my system:
[KM 0 2022-01-19_16-20-09]
All I did was uncheck this setting and I've had no further sluggish/non-responsive behaviour.
By way of explanation, this setting determines whether or not KM proactively w…
2 Likes
Oddly enough, I checked and that's already ticked. It seems to be behaving at the moment, but if it crops up again I'll be sure to check that menu item. Thankyou!
It's still misbehaving, so I wrote this:
KM - Always Evaluate.kmmacros (28.6 KB)
Screenshot