Releases: CuteMoonGod/EZ-Action
v1.0 - Hotfix
Contains a hotfix for a bug that I overlooked that caused the code for progress bars to not be output!
v1.0 - Release 1
With EZAction done to a point I feel comfortable releasing, here it is!
This version includes mostly redone UX stuff to make stuff easier to follow and use. Any problems? Send me a message or open an issue!
What's Changed
- RC4 merging by @CuteMoonGod in #42
- Code improvements by @CuteMoonGod in #43
Full Changelog: v0.3.1...v1.0
Contributors
Assets 4
v0.3.1-RC3-v2
Contains the fixes as described in #29
Major changes:
- The editing label is now a catch-all label for minor messages
- Redesigned and less fugly toolbar
- Renamed and (hopefully) clearer code proxies
A more detailed list is found in the PR, which links to every issues this release closed.
v0.3.0 - RC3
RC 3 of EZ-Action
This release (candidate) includes the project mode, the ability to edit existing actions, code proxies for the conditions and some minor changes.
Editing Actions:
See #2
Any action that exists already can be double clicked in the action list. Doing so will load it's settings back into the window's boxes for you to edit.
Some functionalities are disabled during this, meaning that you have to save your changes first to pick another action, delete an entry or export the current list.
Code proxies:
See #3 & #6
In essence, this is the first step of introducing code proxies to the program.
These are variable functions that are declared at the top of the output file so that, in the best case, the user doesn't have to touch any generated function and can just write their behavior and conditions in the header of the file.
This RC only contains the conditions part of the issue while we investigate how to properly implement the behavior part.
"Project Mode":
See #4 and it's subtasks
By far the biggest change to the program is the introduction of the "Project Mode". The project mode allows the user to save their progress to a file on their PCs and then later on come back and make changes to it, add new actions or even use specific structures as a code template, if desired. It could be especially helpful for larger action trees or complex interactions and I'm excited to see if this will turn out to be a valuable addition to the program.
This was a far larger undertaking than I thought but happily finished and I'm quite proud of how it turned out!