I have frame animation on each cell.
On 30 апр, 18:24, Romain Guy wrote:
> Why don't you just use a LayoutAnimation? That's what it's for.
>
> 2009/4/30 Illidane :
>
>
>
>
>
> > I did that ( write somewhere in getView ) :
> > if(position == mGameModel.getCount() - 1)
> >(
Why don't you just use a LayoutAnimation? That's what it's for.
2009/4/30 Illidane :
>
> I did that ( write somewhere in getView ) :
> if(position == mGameModel.getCount() - 1)
> (new Timer(false)).schedule(new AnimationTimer(), 10);
>
> AnimationTimer() just run my animati
mGameModel.getCount() - it's number of Grid elements)
On 30 апр, 13:07, Illidane wrote:
> I did that ( write somewhere in getView ) :
> if(position == mGameModel.getCount() - 1)
> (new Timer(false)).schedule(new AnimationTimer(), 10);
>
> AnimationTimer() just run my anim
I did that ( write somewhere in getView ) :
if(position == mGameModel.getCount() - 1)
(new Timer(false)).schedule(new AnimationTimer(), 10);
AnimationTimer() just run my animation. Without this timer when I was
trying to write if(position == mGameModel.getCount() - 1) my a
Hello Guys,
Even I am facing such a problem, where I need to detect when all the
calls to getView() are done. After this I want to perform my animation
on only one children in the view. Looks like thr is no straight
forward way to detect the completion of getView(). Is there a way by
which I can
Good to hear!
I'm curious: what did you do to get around this problem?
(yarik may want to know as well :-))
On Apr 29, 11:13 am, Illidane wrote:
> No matter.. it's all working now with the GridView, I have fixed that
> bug by the hand.
> Thank you for your help)
>
> On 29 апр, 17:07, Streets Of
No matter.. it's all working now with the GridView, I have fixed that
bug by the hand.
Thank you for your help)
On 29 апр, 17:07, Streets Of Boston wrote:
> If you have all 100 cells visible at once at all time, the GridView
> does not add much functionality (no scrolling necessary), except for
If you have all 100 cells visible at once at all time, the GridView
does not add much functionality (no scrolling necessary), except for
selecting cells.
I'm not familiar with your app, but i think it would be 'easier' than
wrestling with GridView to subclass 'View' (or 'ViewGroup' if you need
ad
Extend the GridView or write my own class which will manipulating 100
cells as drawables?
On 29 апр, 00:27, Streets Of Boston wrote:
> I have to defend Romain here.
> The gridview and/or listview is just not designed to do this. You're
> trying to put a round peg in a square hole.
>
> Maybe the
I have to defend Romain here.
The gridview and/or listview is just not designed to do this. You're
trying to put a round peg in a square hole.
Maybe the decision to use a GridView for your purposes is not a good
idea, because of its design that does not fit what you need.
If all 100 cells are vi
Thank you for your replying)
How I'll know what delay I need to put into the postDelayed?
It can be different on real device, or user can run too many apps and
my will be running slowly, so getView will be calling too long.
On 28 апр, 18:57, Streets Of Boston wrote:
> Yikes
>
> Another opti
Ok-ok, I gotcha what you mean.
But with such position to developers you will never make android lead
platform.
Sory, if I speak the truth boldly.
On 28 апр, 19:44, Romain Guy wrote:
> No, you are just making assumptions about how it should work. Nowhere
> does it say that it should work the way
We have three times same value of pure the magical-generated position
and the official answer "it is NOT a bug". Ok, than I am Al Pacino.
Why not to post algorithm of position generating? That looks fishy...
On Apr 28, 7:44 pm, Romain Guy wrote:
> No, you are just making assumptions about how i
No, you are just making assumptions about how it should work. Nowhere
does it say that it should work the way you want it to work, that's
not how it works and that's not how it will work.
2009/4/28 Illidane :
>
> To Romain Guy:
> Ok, I understood that you think that it's NOT a bug and that you
>
To Romain Guy:
Ok, I understood that you think that it's NOT a bug and that you
implement it how you want it be.
But I need to say you, that in such situation is very hard, or
sometimes is impossible to write good, stable, beauty, useful and
competitive apps for Android, not only for me, but for a
Yikes
Another option would be to start a timer at each getView call (using
postDelayed and removeCallbacks methods; postDelayd to start timer,
removeCallbacks to remove previous timer until the last call to
getView).
When the last timer times-out (the last non-remove postDelayed), the
task (
I am from the Google team (and I did implement a lot of GridView and
ListView) and it is NOT a bug. GridView and ListView can call
getView() out of order and more times than the number of views that
will fit on screen, depending how the Grid/ListView is measured/laid
out.
2009/4/28 yarik...@gmail
I have tried to do that - doesn't working for me :(
Animation is running always without last cell.
I think so:
In first case there is a '0' at the end of position values. Without
your algorithm all 100 animations is running, than without last ( and
there is no '0' at the end ).
With you alhorithm
Don't rely on the order in which getView is called. It is not a bug.
It is a decision of the design of the grid/list view not to be
dependent on the order in which getView is called. Why getView with
position '0' is called three times... i don't know. *If* this is a
bug, it is only a peformance is
I have exactly same problem. Why do we have 102 values of position
when there is only 100 cells displayed on screen?
"position is changed like: 0, 0, 1, 2, 3... 99, 0" - what is the cause
of that? Can someone from google team answer?
That seems to be a bug, very annoying bug. Answer "It's not a bu
There is a way to make GridView without Adapter ( e.g. something
like .addView() method ) ?
On 27 апр, 21:38, Illidane wrote:
> My GridView shows all 100 cells on the screen ( all visible at one
> moment )
> and all the animation works fine, and pretty fast ( on all 100
> elements ),
> but than
My GridView shows all 100 cells on the screen ( all visible at one
moment )
and all the animation works fine, and pretty fast ( on all 100
elements ),
but than begin problems with last cell.
Animation not child-view's. Each cell is a imageView with animation on
it.
On 27 апр, 20:43, Streets Of B
It's not buggy. I use the adapters and grid/list-views in my apps and
they work fine. I think they are not designed for your purpose.
e.g. If your adapter has 100 elements and the grid/list-view only
shows about 15 at a time on the screen, the getView is called about 15
times. Sometimes more time
And you think it's not a bug? where is guarantee that it will work in
general?
Where adapter takes it's magic number N?
On 27 апр, 19:56, Romain Guy wrote:
> There is no guarantee it's going to be called N times either.
>
> 2009/4/27 Illidane :
>
>
>
>
>
>
>
> > Even with convertView problem is
There is no guarantee it's going to be called N times either.
2009/4/27 Illidane :
>
> Even with convertView problem is still same - last cell is not
> animating.
> And... you said WHEN getView()... I think it's no matter, matter HOW
> MANY times getView() called.
> It calls more than 100 times,
Even with convertView problem is still same - last cell is not
animating.
And... you said WHEN getView()... I think it's no matter, matter HOW
MANY times getView() called.
It calls more than 100 times, whats very strange.
For the first time it's called 102 times and all animations was
working. For
You should ALWAYS reuse the convertView, oherwise you're gonna eat up
memory and just slow down your app. And like I said, there is no
guarantee on how and when getView() is called so you cannot rely on it
with your anim counter.
2009/4/27 Illidane :
>
> I dont use convertView parametr and return
I dont use convertView parametr and return new child-view.
Each cell has an animation. In the getView I generate an array of
animations, wich I start when the adapter stops his work ( e.g. when
my mAnimCounter == 102 ( but need be max 100, lol ) When I run app,
all 100 cells are animated. But whe
The child/item-views in list-views and grid-views are re-used
(convertView input parameter). I suspect that depending on the layout/
measurements/visibility of the child-views and the way you implement
getView (re-using convertView or ignoring it and returning a brand-new
child-view every time), t
Why number of getView calls is different??
One time it's 102 ( but need to be 100 ) and the second and greater is
101.
On 27 апр, 18:15, Romain Guy wrote:
> It's not a bug. There's no guarantee in the order of the calls wrt to
> the position value. It also depends on how the GridView is
> measur
It's not a bug. There's no guarantee in the order of the calls wrt to
the position value. It also depends on how the GridView is
measured/laid out.
On Mon, Apr 27, 2009 at 6:38 AM, Illidane wrote:
>
> Hi,
> I'm using GridView in my app, and myAdapter ( extends BaseAdapter) for
> it. I have overr
31 matches
Mail list logo
