@Tim P For this specific example subclassing would do the trick. Store
xas a property and print it's value in the Action event handler. Set the period as desired, and for extra accuracy confirm the time between prints before printing.
If i do that, then I need to create a simple parser and then create a class on the fly (Xojo doesn't support that).
I hope XojoScript have Ptr datatype or we can use AddHandler or a Delegate, Or passing object datatype back to Xojo code.
You want to open a new case. The other one is closed now. Just mention in yours that it is apparently a regression, and link to 370.
At any rate, it should be fixed. The only way to get attention from Xojo engineers is a bug report.
In practice, you may want to test with 2015R3, since Travis hill apparently tags it as fixed.
You should attach the one that demonstrates the high CPU usage to your bug report.
@AsisPatisahusiwa I solved this issue by creating a simple Linux plugin to provide delay function. Now, average CPU usage is 10.0%.
Thank you all. I'll create feedback for this issue.
Well for what it's worth, that high usage test project has nothing weird about it that I was expecting to see.