Christopher Whitley

Sounds good. Wonder it a separate issue should be made to discuss this specifically. There are other questions and concerns about this that I feel specific guidelines would help in...

@SimonDarksideJ there are almost 900 members missing XML documentation. Here is a tracking spreadsheet I setup from a build output https://docs.google.com/spreadsheets/d/1CMKClYiAuwbw1M7vMwqQFRj-Loq6a7VmTpqbb1HiNTE/edit?usp=sharing The value added would be so that it's fully...

I've created Issue #8165 to track the specific discussion of updating the XML documentation

Thanks for the suggestion @mk1024, I'll look into this. I'm currently working on updating the core part of the lib to use the new released AsepriteDotNet, so it may be...

1.3-rc2 changes were all Aseprite side that updated UI specific components or bug fixes. Nothing of note that I can find was added that would need to be implemented in...

With the release of `MonoGame.Aseprite` version 4.0.0, the library is compatible both with Aseprite 1.2 and Aspeirte 1.3 beta. Anyone having this issue, please update to the new version if...

Closing this issue, tracking will now be done in issue #43

## The Problem I've been going back and forth on this for a bit now since the v4 update, and I'm struggling to see how I can make this possible....

With the new version of `MonoGame.Aseprite` it's now possible to create custom cycles for animations in the `SpriteSheet`, even after import of the AsepriteFile. However, it is still not possible...

@fossegutten Starting with Version 5.0.0, when using (minimum) Aserpite 1.3-rc1, tags now have a "Repeat" property which can be set to specify that the animation should only play once.