B4A Library NineOldAndroids

This is my version of the NineOldAndroids lib for B4A. It's free and provided with the Java source code.

This library offers more possibilities of animation than AnimationPlus (rotation or translation on more than one axis for 3D effect, animation step by step with events for each step, synchronization between animations, ability to change the view size and contents during the animation, etc.).

It works with all versions of Android >= 2 and with all views, even custom ones.

v0.92: Initial release.
v0.92b: I changed the package name and repackaged the source to ease its compilation.
v0.93: I fixed a bug in noaObjectAnimator.InitializeFloat.

 

[Star-Dust]

Some rare versions of Android 7 do not rotate with native commands.
For example on some Huawei

This link seems to confirm that RotationY does not work on Huawei devices with Android 7:
https://stackoverflow.com/questions/45477454/rotation-y-not-working-on-some-phones

Does the label demo work on your device? It rotates a label, not an imageview.

I confirmed it already before.
I text my Apps on 10 different devices, to be more professional, including Huawei devices.
And on the Huawei devices with Android 7 the native rotations do not work

See in this my post: https://www.b4x.com/android/forum/threads/view-utils-snippets-on-android-7.93082/#post-589055

 

[Informatix]

Unfortunately no one can do anything to fix this except Huawei.

 

[Star-Dust]

Unfortunately no one can do anything to fix this except Huawei.

You are able to create functions that allow the rotation without using the API

 

[Informatix]

You who are good you can create functions that allow the rotation without using the API

These functions are in libGDX.

 

[Star-Dust]

However, he did not satisfy the need, because I believe he was looking for functions that would allow him to move the Pivot point into space.
Not only for X and Y but also for the Z axis.

I like the idea of creating a function that makes 3D projections.
Many years ago I made a similar one using Sin and Cos in Turbo Pascal on a 486, but I do not know if there is enough computing power with B4A to have fluidity in the movement

 

[LucaMs]

Does the label demo work on your device?

no

 

[Informatix]

no

It was just to confirm that's not restricted to ImageViews; it's at the view level that the code is broken.

 

[Informatix]

However, he did not satisfy the need, because I believe he was looking for functions that would allow him to move the Pivot point into space.
Not only for X and Y but also for the Z axis.

I like the idea of creating a function that makes 3D projections.
Many years ago I made a similar one using Sin and Cos in Turbo Pascal on a 486, but I do not know if there is enough computing power with B4A to have fluidity in the movement

libgdx supports the Z axis. You can see that in two examples.

 

[LucaMs]

Well, I can conclude that:

1) I would not like to denigrate the work of others and in fact I was not doing this at all, I have only found of a problem on my device with Android 7;

2) some people like to attack others and believe they are superior to others.

I WANT to repeat that:

if I'm not mistaken, the library seems to not work on Android 7

Fortunately we are not all the same.


I have nothing else to say.

 

[Informatix]

2) some people like to attack others and believe they are superior to others.

Some people are paranoid also and think that other people attack them while they don't.

 

[LucaMs]

Some people are paranoid also and think that other people attack them while they don't.

"you make confusion" and say that I should have written "I don't know how" are certainly not compliments, do not you think?
and the Likes indicate that other people agree on your sentences.

Maybe I'm paranoid but I prefer my faults to those of other people.

 

[Informatix]

"you make confusion" and say that I would write "I don't know how" are certainly not compliments, do not you think?
and the Likes indicate that other people agree on your sentences.

View attachment 67965

I wanted to tease you a little and you took it hard. Okay, my apologies. Whatever, that didn't stop me from trying to verify what you told me.

Fortunately we are not all the same.

Saying some people, including you in an implicit way, do not have this behavior flaw is another mean to say "fortunately there are superior people to them". The snake bites its tail.

 

[Star-Dust]

These functions are in libGDX.

There seems to be a solution, change the value
CameraDistance that in the Huawei device is default set to 0

 

[LucaMs]

Whatever, that didn't stop me from trying to verify what you told me

After I pointed out to you that I did not mean to denigrate your library; maybe you had this feeling.
And I must say that I had appreciated this and also understood.
In fact, I was very undecided whether to block your posts too; I was wrong to do this.

Saying some people, including you in an implicit way, do not have this behavior flaw is another mean to say "fortunately there are superior people to them". The snake bites its tail.

I wrote something different (but obviously I wrote it using my bad English).

 

[Informatix]

There seems to be a solution, change the value
CameraDistance that in the Huawei device is standard set to 0

Some findings about the subject:
https://www.b4x.com/android/forum/threads/view-utils-snippets-on-android-7.93082/page-2#post-589176

According to the documentation, the default value of the CameraDistance property is supposed to be = 1280 * Density.

 

[LucaMs]

According to the documentation, the default value of the CameraDistance property is supposed to be = 1280 * Density.

Not exactly, I think:
The distance is expressed in "depth pixels." The default distance depends on the screen density. For instance, on a medium density display, the default distance is 1280. On a high density display, the default distance is 1920.

 

[Informatix]

Not exactly, I think:
The distance is expressed in "depth pixels." The default distance depends on the screen density. For instance, on a medium density display, the default distance is 1280. On a high density display, the default distance is 1920.

1920 = 1280 * 1.5 (high density)
It's explained on the last line.

 

[LucaMs]

Not exactly, I think:
The distance is expressed in "depth pixels." The default distance depends on the screen density. For instance, on a medium density display, the default distance is 1280. On a high density display, the default distance is 1920.

Then we need to check the distance set on the device:

Dim jo = v As JavaObject
Dim DefaultDistance As Float = jo.RunMethod("getCameraDistance", Null)
Log("Device camera distance: " & DefaultDistance)

 

[Informatix]

Then we need to check the distance set on the device:

Dim jo = v As JavaObject
Dim DefaultDistance As Float = jo.RunMethod("getCameraDistance", Null)
Log("Device camera distance: " & DefaultDistance)

On my main device:
Distance = 3840
Density = 3
1280*density is confirmed.

 

[LucaMs]

On my main device:
Distance = 3840
Density = 3
1280*density is confirmed.

On my tablet (ASUS) too: 1280, since scale is 1

on my Huawei it is... -0

So I must set it using:
GetDeviceLayoutValues.Height * GetDeviceLayoutValues.Scale

but this also seems conditioned by the orientation of the device, when you create an animation.