BUG(?) -Animation Lib

[Cableguy]

I am trying to animate a view, by making it slide across the screen...
I place the view in the designer and set its LEFT prop.
I found this to happen with my animation:
If the view is on screen, that is to say within the activity, the animation works flawslessly. The same is true even if the Left =0-width + 1, so a 1dip portion is still visible on screen.
As soon as I set the Left prop of the view (starting point of the animation), to be off screen (Left=0-Width), the animation doesnt play.Same with the visible =false, wont play.
So from what I can see, we cannot animate an invisible view, even if we have setted it visible just before the animation.start, nor we can animate offscreen views.

Is this a BUG , a limitation or am I overlooking something?

 

[Cableguy]

I tried to duplicate this behaviour in a Test app, but all seems to work fine, so I think it's some interaction with one of the libs I'm using in my project...

My Project is based on the Kalendar Picker with some improvents and changes to suite my needs...

Panel2 is the one to be animated, and has it's Top Value set to 508 wich renders the anim NOT to play, but if I set it to 507 it plays, but shows a 1 line high portion of the control on its "idle" state..

Any one has any idea why this is happening?

 

[Erel]

You can move the view to the working position just before starting the animation. I'm not familiar with this specific issue however the native Animation code is far from being perfect.

Similar thing is done in SlidingPanels code.

 

[Cableguy]

Got it into working condition and I am happy with the result...Still I cannot understnd why it works in an empty project file...so this has to be some interaction with a library, I guess...

Another issue I had in this project, related to the same, is the repeat_reverse mode didn't work, so I had to re-initialize the translate movement...no biggy, but I don't know how the repeating initializations are going to affect memory usage, as they lay on an If Then statement in the activity key press event...