Phase • Animations made easy!

Extensions
, ,
#317

Is this extension still active?

image
image2831×264 138 KB

#318

you got the no such class error…

How to avoid runtime errors with the companion app

  1. After importing an extension, please restart the companion app.
  2. If you like to use an extension on a different screen, in Screen1 additionally drag the extension into the working area.

While starting the companion app, all necessary assets and also the imported extensions of your project will be copied to your device. So in case the no such class error shows up, the extension code to run the extension is not available on your device. Without that code the companion app is not able to execute methods from the extension.

In case restarting the companion app does not work for you after trying several times, then as it looks like the only way for you to test you app will be after building it using the apk file.

Taifun

1 Like
#319

:sparkles: Phase v3.0 :sparkles:

After almost 2 years, here we are again with a new version of Phase. This release was mostly motivated by the recent addition of helper blocks in AI2; I wanted to test if they worked in Rush and what would be better than to test them on my own extension. Along with the helper blocks, I managed to sneak in a handful of new things.

This release deprecates all the property-type animation technique blocks in favor of the new helper blocks. You should still be able to upgrade to this version without breaking any of your existing projects. Although not mandatory, it’s recommended that you switch to new counterparts of the deprecated blocks.

Changelog :eyes:

  • Switched to helper blocks for animation techniques – The old property blocks are now deprecated.

    • tech-tada

    • tech-wave

  • Added AnimateComponent2 method – This is a simpler counterpart of the original AnimateComponent method but with fewer parameters. It is perfect when you want a quick way to animate something and don’t need to listen to any events.

    animate-comp-2
    animate-comp-2960×214 24.9 KB

  • Deprecated the CancelAnimation, PauseAnimation, and ResumeAnimation methods – These were ambiguous and didn’t really play well with the ID system.

  • Added Cancel and CancelAll methods – These can be used to cancel running animations. When you cancel an animation, the component associated with it is brought back to its original state (the state before the animation started). Both of these methods trigger the AnimationCancelled and AnimationEnds events. Has no effect on already canceled animations.

    • cancel

    • cancel-all

  • Added Pause and PauseAll methods – These can be used to pause running animations. Triggers the AnimationPaused event. Has no effect on already paused or cancelled animations.

    • pause

    • pause-all

  • Added Resume and ResumeAll methods – These can be used to resume previously paused animations. Triggers the AnimationResumes event. Has no effect on already running or canceled animations.

    • resume

    • resume-all

  • Added IsRunning and IsPaused methods – These can be used to determine the state of an animation.

    • is-running

    • is-paused

  • Fixed a bug that allowed the use of duplicate IDs – You’ll now be greeted with an exception if you try to use a duplicate ID.

  • The ID system has been reworked internally. This along with the new blocks for canceling, pausing, and resuming animations should remove the need for having multiple instances of Phase when dealing with a lot of animations simultaneously.

  • Other internal changes.

Downloads :arrow_down:

Direct: io.shreyash.phase.aix (68.2 KB)
Google Drive: https://drive.google.com/file/d/1fviQil8GOeSvVWMKMOxG1Hi82M4qOCNQ/view?usp=drive_link

Links in the first post have been updated as well.

So, that’s it for this release. I thought the extension was technically done after the last release but I guess no software can ever be called done, there’s always something to improve. :grin:

As always, feel free to provide suggestions and report bugs here. If you like my work and feel like supporting it, you can now do that here – https://ko-fi.com/shreyash

Cheers,
Shreyash

5 Likes
#320

:sparkles: Phase v3.1

Changelog :eyes:

  • Fixed the java.lang.Error: Cannot init easingMethod instance exception that would show up on some animation techniques. [ref]

Downloads :arrow_down:

Direct: io.shreyash.phase.aix (81.1 KB)
Google Drive: https://drive.google.com/file/d/1fviQil8GOeSvVWMKMOxG1Hi82M4qOCNQ/view?usp=drive_link

Cheers,
Shreyash

9 Likes
#321

Hi, your extension is so useful and a lifesaver. I have been using it for a long time.
I just wanted to ask about an error, I’m receiving using it now with Companion:

image
image972×249 72.9 KB

Is the extension no longer working with the latest Kodular?

Thanks

Edit: Nevermind, I solved the issue. It’s the Technique block, I just used a text component like the old Kodular, these custom selection comps are not working for me, not sure others. Thanks again

#322

Make sure that you restart the companion after upgrading the extension. If that’s already done, try hard resetting the connection.

3 Likes
#323

Actually, I am getting errors while adding phase extension in my app and the error is showing Landroid/support/v4/view/ViewCompat; please help me

#324

I had the same error.
The old block wasn’t working.

Use this block

as follows:

#325

Hi! I have some issues in one of my screens, in the others I use Phase the animation works. This error shows up in companion when trying to execute an animation.

imagen

These are my blocks

imagen

Thank you!! Sorry for bothering!

#326

Whenever I try to do an animation it is giving me this error: Error from companion: no part ‘invoke’ in package yail, unknown, version 0.0

The weird thing is that is was working before. I have not added any components. I have edited the code slightly, but nothing related to the animations.

Edit:

It works now with text blocks. Weird that it worked before with the technique blocks

#327

i have same isssue when using companion , no problem with apk

#328

How can i ignore already running animation error , im already used “when screen error occured” but still this error pops up with end application button