v1.0.0 Public Release (LTS) is the first public release of Shime out of beta. This release is a long-term support release and will be supported for at least 1 year. This release is a major release, and is not backwards compatible with previous releases.
Documentation will be updated to reflect the changes in this release soon.
Changelog:
[BREAKING]: Removed Shime.IsPlaying, Shime.IsPaused, and Shime.IsStopped.
Added Shime:GetFrame() and Shime:GetGradient() to get the Frame and UIGradient instances used by Shime. This allows for more customization of Shime.
Added Shime.PlaybackState: Enum.PlaybackState to replace Shime.IsPlaying, Shime.IsPaused, and Shime.IsStopped.
Do you use Shime and want to get your work featured? We are looking for any works made with Shime to feature our materials. Get your work along with your name and link shown as official examples.
v1.0.1 Parameter Validation (LTS) improves stability and error handling for Shime. It adds some minor changes overall while keeping Shime’s functionality the exact same. Improved error handling and links to the Shime wiki.
Changelog:
Add wiki links to the boilerplate of Shime so people know how to use the module.
Add parameter validation which will print more concise and readable errors.
I’ve found a problem with the Shime module. The problem is that the frame that create that shimmer effect, and even after the animation, they remain and there are a lot of them if i’m entering end leaving for so many times the button or the UI object. I’ve tried to remove the ‘UIShimmer’ frame but the for loop doesen’t find any of those frames. Any solution?
UIShimmer hosts the UIGradient used for the shimmer effect. You shouldn’t remove UIShimmer unless you plan to no longer use a shimmer effect on the GuiObject.
I don’t know what you exactly mean by “if i’m entering end leaving for so many times the button or the UI object”.
You can play the shimmer effect again after it’s over by calling :Play() again instead of using .new() if you are doing that.
FYI, Stop() is missing. Seems to have been removed.
Also, I had to add a pcall to the padding offset update function because if you Destroy() it, the GetPropertyChange fires for Parent and nil doesn’t have UIPadding.