OptionMenu layout bug when using Dialog theme?

by Daniel » Fri, 13 Mar 2009 15:06:22 GMT


Sponsored Links
 Hi,
I did an Android application which just has an AutoCompleteTextView.
The Activity containing the AutoCompleteTextView uses the Dialog theme
(android:theme="@android:style/Theme.Dialog").
This Activity also has an options menu. But when you press the options
menu button the menu is displayed right below the AutoCompleteTextView
which is somewhere in the middle of the screen, not at the bottom.
I found no way to display the options menu at the bottom of the
screen. Is this a bug?
--~--~---------~--~----~------------~-------~--~----~



OptionMenu layout bug when using Dialog theme?

by Romain Guy » Fri, 13 Mar 2009 15:29:50 GMT


 Known bug which I think we fixed in Cupcake. Note that having a menu
for a dialog is very weird anyway.






-- 
Romain Guy
Android framework engineer
romain...@android.com

Note: please don't send private questions to me, as I don't have time
to provide private support.  All such questions should be posted on
public forums, where I and others can see and answer them

--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


OptionMenu layout bug when using Dialog theme?

by Daniel » Fri, 13 Mar 2009 15:40:40 GMT


 The AutoCompleteTextView is to build something like a desktop search
(Apps, Music, Contacts etc).
But I also need a way to jump into the settings dialog. Therefore I
need an options menu on a dialog style activity. Looks pretty nice ;-)




--~--~---------~--~----~------------~-------~--~----~



OptionMenu layout bug when using Dialog theme?

by Daniel » Fri, 13 Mar 2009 15:43:11 GMT


 still not fixed in Cupcake (03/03/2009). :-(




--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. TIME_TICK in an AppWidget?

I'm trying to build a custom clock AppWidget, one that I can't base
off of the standard AnalogClock or DigitalClock. I'm doing my best to
keep its updates lightweight, but nonetheless, it needs to update once
a minute. The TIME_TICK broadcast action seems the obvious way to go
about it - but as the docs state, "You can not receive this through
components declared in manifests, only by exlicitly registering for it
with Context.registerReceiver()." Problem is, I can't use
Context.registerReceiver() in the AppWidget, because  it's a
BroadcastReceiver itself.

Anyone have an idea how I might get TIME_TICK in an AppWidget, or
another way to get an update each minute? I considered the
updatePeriodMillis attribute in the provider XML, but that won't let
me sync the update to the minute-changeover, it would only trigger an
update at some time during the minute.

Any tips would be appreciated. Thanks!

String

--~--~---------~--~----~------------~-------~--~----~

2. RTSP stack implementation

Hi,
I am working on making RTSP url to work on Android.

1. I have used MediaPlayer and VideoView to play the RTSP url but both
of them fail to play in G1 Device and emulator. Error is
PVMFFailureiin PLAYER_INIT.

2. So I thought of implementing a RTSP client from scratch. I have
developed a small application, it exchanges all the messages
(DESCRIBE, SETUP, PLAY, TEARDOWN). But the problem is after PLAY, I
should receive the RTP packets at client_port as mentioned in
Transport header but TCP dump shows the following messages. I think
UDP packets are coming but not received at the application.

11:38:50.213394 IP ew-in-f177.google.com.6970 > 192.168.1.2.6970: UDP,
length 444
11:38:50.213451 IP 192.168.1.2 > ew-in-f177.google.com: ICMP
192.168.1.2 udp port 6970 unreachable, length 36

Please let me know how to solve this issue.

With Regards
Vinayakumara T V
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

3. Port AbsoluteLayout to any other Layout to draw at x,y position

4. Keeping Surface View subclass working through orientation change?

5. Orientation Sensor return false values. And getRotationMatrix() also doesn't work. Is my ADP1 broke?

6. Force Close pop up when uncaught exception during background service

7. Full browser vs WebView view