ContextMenu on TableLayout: how to get selected item position?

by Atif Gulzar » Mon, 25 Jan 2010 13:59:10 GMT


Sponsored Links
 I had the similar issue and solved it with a work around. In your table row
add a TextView and makes its visibility GONE and set its text as 0,1,2,4...
for respective rows. Add a single listener for each row. When some row is
clicked the listener will give you a clicked view. From this view get the
text view from this text view the index.





--
Best Regards,
Atif Gulzar

I  Unicode, zln 






>



Other Threads

1. SQLite insert optimization

Hello!
I have to insert around 100 rows in a sqlite db at once (trough
content provider). Is there any way to make it process all the queries
at once, instead of querying the provider for each row separately.

-- 

2. Fragment transactions, transitions and the back stack

Hi All,
I am having trouble using or understanding how popping
FragmentTransactions off of the back stack handles the custom
animations. Specifically, I expect it to call the "out" animation, but
it doesn't seem to.

I have a simple method to handle a fragment transaction
(FragmentTransaction) where I add a fragment and apply a custom
transition so that it will fade-in/fade-out. I am also adding this to
the back stack so that the user can undo that transaction with the
back button, essentially navigating to the state before the fragment
was added.

Everything works great moving forward, but when the user clicks the
back button, the transition animations do not reverse. What I expected
was that when the fragment got removed, it would use the fade out
animation. Instead it seems to pop out (without animation) and then
the container seems to fade in. I'm not sure that this is exactly what
is happening, but the fragment is definitely not fading out.

Here is the method that handles the transaction:

protected void changeFragment() {
    FragmentTransaction ft = fm.beginTransaction();
    ft.setCustomAnimations(android.R.anim.fade_in,
android.R.anim.fade_out);
    ft.add(R.id.fragment_container, new TestFragment());
    ft.addToBackStack(null);
    ft.commit();
}

My application uses the compatibility library to add fragment support,
but I assume this to be applicable to Honeycomb (android-11) as well.

Does anyone know if I am just doing something wrong here or if I am
just expecting too much? Ideally, I would like to animate the
fragments similarly to how Gmail (on the Xoom) does in regards to
moving forward by clicking a message and then back by using the back
button. Preferably not having to override the back button
functionality and keep up with my own fragment state since I could
have several "transactions" that I would want to back out of and I am
not a fan of re-inventing wheels.


-- 

3. FW: Help needed on Android sensor service/sensor HAL

4. android developer site not working

5. Running Monkeyrunner directly on Android tablet

6. Group

7. UPDATE 2 --- WTI: Info Lengkap Penjualan LG Android Rp 999 Ribu