No new resources needed. Again, please see the complete working examples in ApiDemos. Fwiw, I can't see what the error you are printing has to do with your code (nor did you include the part where it says the line number of the error).
On Tue, Sep 22, 2009 at 12:28 AM, Karthik P <[email protected]> wrote: > I tried that too... I get the following error. > [2009-09-22 12:56:19 - win]ERROR: Failed to parse %1$s > [2009-09-22 12:56:19 - win]AndroidManifest.xml > > > <activity android:name=".win" > android:label="@string/app_name" > android:theme="@android:style/Theme.Dialog"> > > As I understand these are default themes and it doesnt require any change > in my resource files. Am I right? > > Karthik > > > On Tue, Sep 22, 2009 at 12:26 PM, Dianne Hackborn <[email protected]>wrote: > >> You need to set the theme in the manifest. The code sample is missing the >> @ in front of android. There are various examples in ApiDemos of dialog and >> translucent themed activities. >> >> >> On Mon, Sep 21, 2009 at 10:26 PM, Karthik P <[email protected]> wrote: >> >>> I saw the below portion in the documentation, >>> "By setting the theme of an activity to >>> android:theme="android:style/Theme.Dialog", your activity will take on the >>> appearance of a normal dialog, floating on top of whatever was underneath >>> it. You usually set the theme through the android:theme attribute in your >>> Android Manifest.xml. The advantage of this over Dialg and AlertDialog is >>> that Application has a much better managed." >>> >>> I tried to follow this but it throwed up an error saying unable to parse >>> AndroidManifest.xml. I guess you are saying in the similar lines to make it >>> translucent. >>> >>> My AndroidManifest.xml looked like this >>> <?xml version="1.0" encoding="utf-8"?> >>> <manifest xmlns:android="http://schemas.android.com/apk/res/android"; >>> package="com.sample.window" >>> android:versionCode="1" >>> android:versionName="1.0"> >>> <application android:icon="@drawable/icon" >>> android:label="@string/app_name"> >>> <activity android:name=".window" >>> android:label="@string/app_name" >>> android:theme="android:style/Theme.Dialog"> >>> <intent-filter> >>> <action android:name="android.intent.action.MAIN" /> >>> <category android:name="android.intent.category.LAUNCHER" >>> /> >>> </intent-filter> >>> </activity> >>> </application> >>> <uses-sdk android:minSdkVersion="4" /> >>> </manifest> >>> >>> then I tried thru the code using >>> setTheme(android.R.style.Theme_Dialog); >>> >>> Above piece of code has built successfully but still I couldnt see any >>> floating app, the app was occupying full screen. The same experiment I did >>> with Theme.Translucent as well. Any light on this? >>> >>> Karthik >>> >>> On Tue, Sep 22, 2009 at 8:47 AM, Dianne Hackborn <[email protected]>wrote: >>> >>>> There is no need to use SurfaceView for that, just make your own >>>> activity transparent such as with Theme.Translucent. >>>> Anyway, the UI model is designed around having one main fullscreen >>>> activity visible to the user (any number of non-fullscreen or translucent >>>> activities can be stacked on top of it). There is no way to have two >>>> running side-by-side without significant deep cooperation between the two >>>> apps. >>>> >>>> On Mon, Sep 21, 2009 at 8:05 PM, Rud <[email protected]> wrote: >>>> >>>>> >>>>> Just speculating but maybe using SurfaceView with a transparent >>>>> region? The background app might show through the transparent area of >>>>> the foreground app. >>>>> >>>>> Rud >>>>> >>>>> >>>>> On Sep 21, 7:43 am, Karthik P <[email protected]> wrote: >>>>> > Does anyone has an idea of how to split the screen into two? Is it >>>>> possible >>>>> > for me to run an application in one screen and another app in other >>>>> screen? >>>>> > Any help in this regard will be of great help. >>>>> > Karthik >>>>> >>>>> >>>> >>>> >>>> -- >>>> Dianne Hackborn >>>> Android framework engineer >>>> [email protected] >>>> >>>> Note: please don't send private questions to me, as I don't have time to >>>> provide private support, and so won't reply to such e-mails. All such >>>> questions should be posted on public forums, where I and others can see and >>>> answer them. >>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> -- >> Dianne Hackborn >> Android framework engineer >> [email protected] >> >> Note: please don't send private questions to me, as I don't have time to >> provide private support, and so won't reply to such e-mails. All such >> questions should be posted on public forums, where I and others can see and >> answer them. >> >> >> >> > > > > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
