This is an emergency release that fixes a bug on the TreeView plugin sizing calculation. The bug caused a constant calculation of the TreeView width when performing the move_towards animation, ending in high cpu usage.
Many fixes and new features like the image viewer, built-in color picker, support for drawing polygons, introduction of a canvas api and experimental live search!
Mostly a bugs fix release with build system adjustments and a tiny bit of enhancements sprinkled on the top.
Some of the fixes include a correction to the dirmonitor backend detection logic thanks to TomaSajt. Also, the code indentation logic was wrong on some instances and should behave better now thanks to Sentmoraap.
Better colors, better performance, new Diff Viewer, SDL3 port and a seasoned dosage of new features, fixes and enhancements!
Many of the new features and fixes on this release are possible thanks to all the help, suggestions and testing provided by Amer.
One of the most exciting features on this release is the new file and strings differences viewer that was suggested by bananakid, who also provided testing and useful feedback, Thank You!
Here is a preview of the viewer and configuration settings:
Many Enhancements, Fixes, and New Features!
This release includes so many changes that it's a bit hard to summarize — but here we go, so lock your seat belts and enjoy the ride!
First of all, this is the first release to ship with a new default color scheme, moving away from the one used by our ancestors to further distinguish our identity:
Some fixes, build system corrections, and some new features!
This release consists mostly of fixes with some minor new additions. One of the relevant changes is proper handling of BOM on opened documents with a new status bar indicator, which lets you know if the current document has a BOM as shown on the screenshot:
A patch release that includes some nice fixes and additions!
In the past, the code responsible for file system monitoring automatically
unwatched/watched files when an event was received. This behavior was disabled
because it caused indefinite signaling of events, which increased CPU usage in
the autoreload plugin that needs to monitor files independently. However, this
behavior is actually necessary for backends like inotify, where a file would get
automatically unwatched if it was removed, only to be re-added later. One
example of this occurs when performing a git checkout <branch>, which removes
and re-adds files that contain changes, causing a file to be unwatched by inotify.
This release restores the previous behavior and fixes the endless signaling of
file system events, resulting in a better functioning autoreload plugin.
A new week and a new release with fixes and performance improvements!
Over the past few days, various people have helped by reporting issues on the GitHub issue tracker, and this release tackles some of them. One prominent change is the improvement in the way that coroutines are scheduled, resulting in overall better responsiveness and performance of the editor, an improvement that would not have been possible without the testing of AmerM137.
This is a SCALE bug fix release! Release explanation slightly adapted from #152
Since new renwindow api (that allows initializing windows directly in Lua) the main window creation was moved to core.init but, the scale detection code was still been performed before. This meant that loading the default system style was using the incorrect scale causing issues that would only be resolved by manually re-scaling the interface.
This release fixes various issues reported on GitHub, and introduces some new features and enhacements. The big ticket for this release is overall better scaling behaviour. macOS builds now default to the plain software renderer which is faster. This is possible because various releases ago (almost a year?) we introduced functionality to detect the display scale at runtime, meaning that scaling should be properly performed Lua side instead of relying on the renderer. The SDL Renderer (aka "hardware renderer") is still available but since the glyph loading optimizations, it needs some adjustments to better handle the positions and sizes of fonts when the scale is >= 2.