Worked on stability - should solve those problems which crashed server under peak load. Now it should just slow down :D Thanks everyone who became part of that pleasant problem, welcome aboard :)
Added new button to main web page which allow to download archive with the most recent version. It will be fully portable with a config that is separate from the main app. This mechanism has already been tested for a few months in Packs, so should work without major issues.
p.s. Please note that portable version is not available for Stable yet, it will be available right after I will push alpha to stable in the next few days.
T
to Nullable of T
(e.g. int
to int?
) #EA-660 v7569 by GwynVery useful for analysis as it allows to split image to black and white which makes further checks much more simple. E.g. instead of having red HP bar with a lot of shades, you can convert it to black/white image where white is filled area of the bar.
Another image simplification technique, allows to reduce total number of colors in the image. By itself it is mostly useless, but can help in combination with other effects.
Made is to IsMaximized in ExecuteScriptNode is stored in the node itself
Load from preview pane
avoids copying debug dataAwaiting for something is a mandatory part of any automation. EyeAuras constantly does that - timeouts between keypresses, ensuring that capture FPS is consistent, user-driven timeouts in scripts. Default instruments provided by operating system and default methods (like Thread.Sleep
, Task.Delay
and few others) are not accurate enough, so at some point I had to implement a combination of methods which ensured better accuracy.
This mechanism allowed sub-millisecond awaits and worked for the last 5-6 months. Unfortunately, accuracy comes with a cost and for most operations it not really needed.
That is why for the next few months we'll be trying a 3rd version of Sleep(), which is expected to meet middle-ground between accuracy and performance cost. On average, it is expected that it will reach accuracy of up 0.5 - 5ms
.
This means that if you are setting EA to wait for 1ms
, the effective wait time will be in range 1 - 1.5ms
, which is more than enough for most use cases. For larger timeouts, such as 100ms
, it may vary in range of 100 - 105ms
.
To counterweight loss of accuracy, you'll get much better performance. We'll see how it goes in real world scenarios. As a part of development for this feature, I've added integration layer which will allow you to use whatever Sleep() mechanism you see fit for your scenarios. Will post information on this later.
Made is to IsMaximized in ExecuteScriptNode is stored in the node itself
Listen()
to ScriptVariable
- you can now use it instead of WatchCurrentValue
This is the first out of 5 fixes towards performance/startup improvements planned for Q4. As always, such things bear high risks, so please report anything strange you may notice. Difference in startup time should not be very noticeable - it is approximately minus ~10%, so just 1-2 seconds less than it was before. But the most important part is that this fix opens up additional time-saving options which I will exploit in the nearest future.
Releasing new version of editor which is shown any time you links something (AuraIsActive, Enabling Conditions, etc)
The new one is much more flexible, so it will be easier to do any changes there. After current version will be stabilized, I'll add "Recent", "Favourites" and few other improvements I have in mind. Please report any issues you'll find or any improvements you think worth doing - the initial implementation may be buggy at first, but hopefully it will quickly get it to surpass the old variant.
oddessax
oddessax