Select to view content in your preferred language

Detailinfo IdentifyResult ICS

3860
8
01-06-2012 05:29 AM
by Anonymous User
Not applicable
Original User: simra

I guess i found a bug:
In the IdentifyTask Sample when i select on name in the list like this [ATTACH=CONFIG]10976[/ATTACH] in Android 4.0.3 i don't get this [ATTACH=CONFIG]10977[/ATTACH]  detail view like in Android 2.3. Pressing the item in the list does nothing. It also shows nothing in the logcat. We tried it with two different 4.0.3 phones.
0 Kudos
8 Replies
DanO_Neill
Deactivated User
What do you get on Android 4.0.3 platform as a result of selecting a result from the IdentifyTask Sample?  What does the logcat return?  I will look into the sample and test to see if I can reproduce, but any information you can provide about what you are experiencing will be helpful.
0 Kudos
by Anonymous User
Not applicable
Original User: simra

When i select an item from the list it just takes me back to the normal mapview that still shows the callout. The IdentifyResult list has normal data in it, so everything seems fine. The thing is if i select a element from the list it takes me back to the normal view like i said before. I guess the IdentifyResultSpinnerAdapter is supposed to take care of the selection in the list and then show the details dialog? As i stated before, if i repeat the same steps on an 2.3 device everything is fine with the details dialog. And for the logcat i don't get any feedback just the usual garbage collector stuff. Could i use a IdentifyResultSpinner and override the onClick as a workaround for the moment?
0 Kudos
SimonKlein
Regular Contributor
To revive this topic:
i just saw that i get the following error in the logcat if i select one item from the list:
02-21 16:43:40.816: W/InputManagerService(193): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@41a72070
0 Kudos
by Anonymous User
Not applicable
Original User: DineshAtPowel

I get the same problem with Galaxy tab 10.1 (Android 3.2)
0 Kudos
SimonKlein
Regular Contributor
FYI: This is still not working in Version 1.1
0 Kudos
by Anonymous User
Not applicable
Original User: ibramoz

I have the same problem, has someone found a solution?
0 Kudos
AndyGup
Esri Regular Contributor
Simon, Enrique, sounds like you need to open a tech support ticket. They can fully capture the information related to this problem, they can submit a bug fix request, and we'll be able to track the problem.


-Andy
0 Kudos
by Anonymous User
Not applicable
Original User: watershed.web.mapping

Anyone a workaround?

I have the same problem, has someone found a solution?
0 Kudos