Bugfixes/Improvements

• [UI] Fixed a problem with Packs - License Agreement window closure led to app termination. That happened only on the 1st launch.
• [UI] License Agreement Window refactoring - should load up faster
• [UI] Fixed a problem with application manifest which made it so the app had to restart to gain admin priveleges. This still has to be tested on different OS versions

Bugfixes/Improvements

• [UI] Minor bugfixes for PopOut functionality added in the previous version
• [UI] Added Move To Parent option to Aura Tree

Macro/BehaviorTrees - PopOut

Added new convenience feature - PopOut for BTs and Macros. This button allows you to show your Macro or BT in read-only form in a separate window. It is showing state in real-time and allows to execute the tree/macro manually.

Bugfixes/Improvements

• [UI] Fixed alignment of CodeEditor in maximized form

Macro editor - node removal

Improved item removal UX and aligned it with other parts of the program

Links

Changed how Enabling Conditions and References in BTs and Macros look like:

P.S. Note the icon to the left of the path - by clicking on it, you will be taken to that specific item.

Double-clicks in Macros

• C# Script node - when double clicked, code editor will be Maximized
• Nodes with Links in them - when double clicked, you will be taken to the first link in the list

Bugfixes/Improvements

• [UI] Fixed a crash which happened if invalid aura name was set
• [Scripting] Fixed(?) a problem with LoginWidget not working properly
• [UI] Fixed a problem with script messages being duplicated in Event Log

Screen capture - BREAKING CHANGE

For years, Target Window was a prerequisite in all Capture triggers (Image/Color/Text/ML) - EyeAuras worked only with windows. Starting from this version, we'll try a different approach:

• If Target Window is not set, EA will start capturing Primary Screen

What this means in practice?

• previously, clearing Target Window basically stopped Triggers from working. From now on, this will only switch the mode to Primary Screen capture and I would suggest to use Enabling Conditions to control the capture. This is very important! Check your old triggers to ensure that there are no "test" or "leftover" triggers as they will start eating up CPU.
• minus extra step if you're setting up something for a personal use - setting up Target Window in many cases is not really required if you're playing games in Borderless Windowed or other similar modes where the game occupies the entire screen
• as soon as we remove window-related stuff from the picture, working with mouse coordinates becomes more simple - every coordinate becomes absolute
• everything related to clicking on objects on the screen will continue to work as is. If you'll notice some problems - please report

IMPORTANT! Multi-monitor setups are not supported yet. Only the primary screen will be captured. I'll extend support in the future

Bugfixes/Improvements

• [Capture] Fixed a problem with FPS selector - it was not working properly and was showing Range selector even if "Min" option was not set

Authentication improvements

First steps toward offline mode - added new option in Settings which allows the client to function without connectivity to the server, even if the client gets restarted. For now, this is just a few hours, but as soon as I will be sure that the system properly works, this will be extended to days. This option will be removed in the future and will become default behavior of the client.

Bugfixes/Improvements

• [UI] Fixed a problem with Start Minimized not working properly under some conditions

Packing - added Start Minimized and Minimize To Tray

Added two new options in Packaging. Both of them are indended to be used by setups with custom scripts having their own UI. By leveraging Lifecycle Events trigger and C# script creating a custom Blazor Window, you can make it so YOUR user interface will be shown instead of EyeAuras.

Start Minimized

If set, when the app gets fully loaded, main window will be minimized.

Minimize To Tray

If set, the window won't even be displayed on the Taskbar, leaving only your custom window there.

C# Scripting - LoginWidget

Added two new examples which use BlazorWindows - Basic Window and Custom Login. Login Widget allows to very easily integrate EyeAuras authentication into your app. It will get more customizable and extensible when I'll receive first feedback.

Bugfixes/Improvements

• [BlazorWindows] Fixed a problem with Transparent background - if set, the window would become unclickable

New Trigger - Lifecycle Events

This trigger is designed to cover scripting scenarios such as running the script right when the app is opened. For now, there are only two events. We'll see whether some other events such as AppFocused could be useful.

In combination with other packing- and scripting-related features, I am targeting to streamline mini-app creation and make it possible to not bootup main EyeAuras UI at all. This is one of the steps.

Detailed information is available here

Bugfixes/Improvements

• [UI] Minor startup time optimization

C# Scripting - NuGet packing

Using NuGet packages in scripts opens up a lot of new possibilities and is hard to underestimate its importance. But downloading and unpacking packages takes time - not much, but noticeable for end-user. From now on, when you're downloading any Pack, EyeAuras server will analyze your code and pre-download all needed packages.

This benefits:

• startup speed - because all nuget packages are included by default into pack
• stability - because even if something will happen with that specific version of NuGet package that you've used OR there are some Internet problems, your downloaded pack will still work just fine

That change IS NOT retroactive - it will affect only new revisions of packs.

Bugfixes/Improvements

• [UI] Fixed bug which made so Import links taken from AuraLibrary page won't work under some circumstances

C# Scripting - Script Protection - Closed Alpha

In the changelog for the previous version I've mentioned that script compilation will be followed by script protection mechanism. It is extremely rough on edges still, so for a few weeks will be available only to very small group of people. Eventually this will become available for anyone.

How to use it

Script Protection is part of Packaging options and is available only when you've set Compilation Mode to Binaries Only - it does not make much sense to apply it to binaries if you're distributing source code. All you have to do is select desired mode, save options and upload your auras, just like you did before. Ideally, nothing should change for the end-user.

Please note, that infrastructure for this service is still extremely unstable and there could be problems spread everywhere - even if you have access to that feature, it may be worth giving it some time to cool down.

Bugfixes/Improvements

• [UI] Using dots (".") in aura names historically led to a whole group of issues as EA saves auras to your local file system using those names. And usually dot denotes file name from its extension. For now, I've made it so EA will show error when you're trying to rename to a name which contains a dot - just like it currently does for a non-valid names containing special characters.