[android-developers] Re: SlidingDrawer
I mean allowing the user to dynamically change the size of the open drawer. Right now, when you let go, it either springs open or shut. Ah, misunderstood you then. Since there's no 'amount open' callback in the API I guess it's not intended to remain in a partial state, you would have to change the source. As a side note, SlidingDrawer is deprecated in 17 and they advise to copy the source into your project anyway :-) Pent -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: SlidingDrawer
Has anyone figured out how to make it open partially - ie not snap open all the way? I implemented that a few years ago, looking at the layout seems like the height of the SlidingDrawer view is the limited. Pent -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: SlidingDrawer
On Friday, March 22, 2013 12:38:05 AM UTC-7, Pent wrote: Has anyone figured out how to make it open partially - ie not snap open all the way? I implemented that a few years ago, looking at the layout seems like the height of the SlidingDrawer view is the limited. I don't mean staticly changing the maximum height of the open drawer. I mean allowing the user to dynamically change the size of the open drawer. Right now, when you let go, it either springs open or shut. Is that what you implemented? Did you start from the Android source? If so, what did you change? Nathan -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: SlidingDrawer widget hidden by GLSurfaceView while sliding
Hi Paul, Any success on this? I am facing same issue. Regards -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Slidingdrawer hides last element of listview.
android:paddingBottom=16dp... in you listview will do the trick. Set it to whatever dp you require On Saturday, October 1, 2011 12:04:12 PM UTC+1, charlie babitt wrote: Hallo! In my activity I have a list view and I want to have a sliding drawer at the bottom of the screen. The handle of the sliding drawer has a solid image and the size of the whole screen width. The problem now is, that the last row of the list is not visible anymore, since it is below the sliding drawer's handle. What is the best solution to solve it. My layout looks as follows: Activity layout: RelativeLayout android:layout_width=fill_parent android:layout_height=fill_parent xmlns:android=http:// schemas.android.com/apk/res/android fragment android:name=test.sample.ListFragment android:layout_width=wrap_content android:layout_height=wrap_content android:id=@+id/listfragment / SlidingDrawer android:id=@+id/slidingdrawer android:layout_width=fill_parent android:layout_height=fill_parent android:handle=@+id/slidingdrawer.handle android:content=@+id/ slidingdrawer.content include android:layout_gravity=bottom android:id=@+id/slidingdrawer.handle layout=@layout/ slidingdrawerhandle / include android:id=@+id/slidingdrawer.content layout=@layout/slidingdrawercontent android:layout_width=fill_parent android:layout_height=fill_parent / /SlidingDrawer /RelativeLayout My Handle Layout: ?xml version=1.0 encoding=utf-8? RelativeLayout android:background=@drawable/handle_background android:layout_width=fill_parent android:layout_height=wrap_content xmlns:android=http://schemas.android.com/apk/res/android; LinearLayout android:layout_gravity=center android:orientation=horizontal android:layout_width=wrap_content android:layout_height=wrap_content android:layout_centerInParent=true TextView android:textSize=14.0sp android:textStyle=bold android:textColor=@android:color/white android:layout_gravity=center_vertical android:layout_width=wrap_content android:layout_height=wrap_content android:text=News android:singleLine=true android:shadowColor=@android:color/ black android:shadowRadius=2.0 / /LinearLayout /RelativeLayout Do you have any idea how I could fix this? Thanks Charlie -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: SlidingDrawer - Setting height moves the view up
try setting on the SlidingDrawer android:layout_alignParentBottom=true. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: SlidingDrawer - Setting height moves the view up
http://developer.android.com/guide/practices/screens_support.html On 24 jan, 08:42, joaocruz04 jtcru...@gmail.com wrote: Hi, i'm having a problem: i've created a sliding drawer with a specific height, at the bottom of the screen. The problem is, when the height of the SlidingDrawer is set as fill_parent, everything works great, but when i set the height as for instance, 150dip, the SlidingDrawer moves to the top of the screen.. is that a common issue? I can't seem to find any user with same problem :S My code btw: ?xml version=1.0 encoding=utf-8? RelativeLayout xmlns:android=http://schemas.android.com/apk/res/ android android:layout_width=wrap_content android:layout_height=wrap_content SlidingDrawer android:id=@+id/drawer android:layout_height=200dip android:layout_width=fill_parent android:content=@+id/content android:handle=@+id/handle ImageView android:id=@+id/handle android:layout_height=wrap_content android:layout_width=wrap_content android:src=@drawable/ ntrack/ImageView LinearLayout android:layout_height=fill_parent android:id=@+id/ content android:layout_width=fill_parent android:orientation=vertical TextView android:id=@+id/txt android:text=This is some text android:layout_width=wrap_content android:layout_height=wrap_content /TextView Button android:id=@+id/btn android:text=Click Me android:onClick=ClickHandler android:layout_width=wrap_content android:layout_height=wrap_content/Button /LinearLayout /SlidingDrawer /RelativeLayout -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: SlidingDrawer to go full screen
Let your top level layout be a RelativeLayout or FrameLayout -- these each permit multiple views to be in the same position. Let the SlidingDrawer be a direct child of your top level layout. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: SlidingDrawer to go full screen
Hi, I think it will help you. check this link http://www.androidpeople.com/android-sliding-drawer-example-tutorial/ On Feb 11, 12:48 am, Salsero69 vaillancourt@gmail.com wrote: How do I get the sliding drawer to open over the existing layout. I'm having a hard time finding an example and having no luck figuring it out on my own. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: SlidingDrawer handle
Thanks, Bob! Unfortunately, it seems Launcher's handle is not accessible (at least it's not in the SDK). Bummer, will have to reinvent the wheel and make my own :-( -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: SlidingDrawer handle
It looks like you have to dig a little deeper. The images and the layout referencing them are in the Launcher package, which is open source. http://android.git.kernel.org/?p=platform/packages/apps/Launcher.git;a=blob;f=res/layout-land/launcher.xml On Sun, Apr 18, 2010 at 12:04 PM, Pinheiro rui.c.pinhe...@gmail.com wrote: Thanks, Bob! Unfortunately, it seems Launcher's handle is not accessible (at least it's not in the SDK). Bummer, will have to reinvent the wheel and make my own :-( -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: SlidingDrawer handle
It's a quick question you should be asking yourself. More useful than doing it for you, I'll tell you how. Go to your SDK. In the platforms directory, choose your platform version. Inside there is a data directory, and inside that is the system's res directory. Go into the drawables/ directory (most actual images are in e.g. drawables-hdpi/) and look there for what you want. This would probably be a .9.png file; the part before that in the filename would be the id. But many images are actually referenced as part of selectors, etc. These drawables are defined as .xml files in the drawables/ directory. So sometimes you have to work backwards from the actual image to find the appropriate xml file to find the ID you really want. On Windows, you can choose a view for these directories that shows a preview (icon) for each .png file. This makes it a lot easier to locate what you're looking for. Remember, these are accessed with android.R.drawable.id, rather than your own, which are accessed with your-apk-package-name.R.id. The other approach is that if you know a system layout that uses what you're looking for, you can look at that layout and see the ID that it's using. On Apr 17, 9:30 am, Pinheiro rui.c.pinhe...@gmail.com wrote: Hi! Quick question: what is the drawable ID of the handle for the application's SlidingDrawer used in the home screen? Thanks in advance! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group athttp://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: SlidingDrawer issue #1?
The same with me. Just filed a bug report at http://code.google.com/p/android/issues/detail?id=3162 You can go there and star the issue to get notified on changes. wbr, Brian On 19 Mai, 14:47, brindy bri...@brindy.org.uk wrote: Yep, exactly the same here. =) Cheers, Brindy On May 7, 11:27 am, cannehal tomasz.l...@gmail.com wrote: As I said before I have the same issue as Sheepz. It works fine in runtime, but in layout editor in eclipse there is Exception. For me it looks like a bug in plugin. And for forthcoming questions: I am using latest SDK (1.5) and proper eclipse plugin. On May 6, 1:34 am, Sheepz eladk...@gmail.com wrote: if you mean 1.5, yes i am, i have also updated the editors for eclipse as described in the upgrade sdk page. On May 5, 7:06 pm, dan raaka danra...@gmail.com wrote: are you using the latest version of SDK ? On Tue, May 5, 2009 at 4:04 PM, Sheepz eladk...@gmail.com wrote: I took a look at the api http://developer.android.com/reference/android/widget/SlidingDrawer.html and copied their example to a clean sandbox project this is the code: [beginquote] ?xml version=1.0 encoding=utf-8? LinearLayout xmlns:android=http://schemas.android.com/apk/res/ android android:orientation=vertical android:layout_width=fill_parent android:layout_height=fill_parent SlidingDrawer android:id=@+id/drawer android:layout_width=fill_parent android:layout_height=fill_parent android:handle=@+id/handle android:content=@+id/content ImageView android:id=@id/handle android:layout_width=88dip android:layout_height=44dip android:src=@drawable/icon / GridView android:id=@id/content android:layout_width=fill_parent android:layout_height=fill_parent /GridView /SlidingDrawer /LinearLayout [endquote] this gives out the exception in eclipse, but it does run well... does anybody know why this is happening? can anyone else confirm this is happening on their environment? Thanks, Sh On May 1, 11:29 pm, Sheepz eladk...@gmail.com wrote: anyone found a solution? On May 1, 10:03 am, cannehal tomasz.l...@gmail.com wrote: I tkink I have the same issue. For handle I have ImageView and for content I am using LinearLayout with some views inside of it. There is probably problem with eclipse plugin because in runtime it works fine. On May 1, 7:01 am, Sheepz eladk...@gmail.com wrote: anyone else found something here? On Apr 30, 5:43 pm, Sheepz eladk...@gmail.com wrote: okay, that didnt work :( SlidingDrawerandroid:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView02 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/back2/ ImageView ImageView android:id=@id/ImageView02 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer still getting the same message in the ADT only now when launching the app, it simply stalls half drawn instead of giving an error message saying the application threw an exception... On Apr 30, 5:40 pm, Romain Guy romain...@google.com wrote: You must use different views, it doesn't make sense to have the same view, it's going to confuseSlidingDrawer:) On Thu, Apr 30, 2009 at 2:38 PM, Sheepz eladk...@gmail.com wrote: yeah, i figured that might be it, but even after this fix: SlidingDrawerandroid:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView01 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer i still get the same error - i'm gonna try using diffrent views for the content and the handle brb :) On Apr 30, 5:32 pm, Romain Guy romain...@google.com wrote: There is a bug indeed, the exception message says the handle is missing, but the content is missing. Check out the javadoc. I'll fix the exception message. On Thu, Apr 30, 2009 at 2:26
[android-developers] Re: SlidingDrawer issue #1?
Yep, exactly the same here. =) Cheers, Brindy On May 7, 11:27 am, cannehal tomasz.l...@gmail.com wrote: As I said before I have the same issue as Sheepz. It works fine in runtime, but in layout editor in eclipse there is Exception. For me it looks like a bug in plugin. And for forthcoming questions: I am using latest SDK (1.5) and proper eclipse plugin. On May 6, 1:34 am, Sheepz eladk...@gmail.com wrote: if you mean 1.5, yes i am, i have also updated the editors for eclipse as described in the upgrade sdk page. On May 5, 7:06 pm, dan raaka danra...@gmail.com wrote: are you using the latest version of SDK ? On Tue, May 5, 2009 at 4:04 PM, Sheepz eladk...@gmail.com wrote: I took a look at the api http://developer.android.com/reference/android/widget/SlidingDrawer.html and copied their example to a clean sandbox project this is the code: [beginquote] ?xml version=1.0 encoding=utf-8? LinearLayout xmlns:android=http://schemas.android.com/apk/res/ android android:orientation=vertical android:layout_width=fill_parent android:layout_height=fill_parent SlidingDrawer android:id=@+id/drawer android:layout_width=fill_parent android:layout_height=fill_parent android:handle=@+id/handle android:content=@+id/content ImageView android:id=@id/handle android:layout_width=88dip android:layout_height=44dip android:src=@drawable/icon / GridView android:id=@id/content android:layout_width=fill_parent android:layout_height=fill_parent /GridView /SlidingDrawer /LinearLayout [endquote] this gives out the exception in eclipse, but it does run well... does anybody know why this is happening? can anyone else confirm this is happening on their environment? Thanks, Sh On May 1, 11:29 pm, Sheepz eladk...@gmail.com wrote: anyone found a solution? On May 1, 10:03 am, cannehal tomasz.l...@gmail.com wrote: I tkink I have the same issue. For handle I have ImageView and for content I am using LinearLayout with some views inside of it. There is probably problem with eclipse plugin because in runtime it works fine. On May 1, 7:01 am, Sheepz eladk...@gmail.com wrote: anyone else found something here? On Apr 30, 5:43 pm, Sheepz eladk...@gmail.com wrote: okay, that didnt work :( SlidingDrawerandroid:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView02 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/back2/ ImageView ImageView android:id=@id/ImageView02 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer still getting the same message in the ADT only now when launching the app, it simply stalls half drawn instead of giving an error message saying the application threw an exception... On Apr 30, 5:40 pm, Romain Guy romain...@google.com wrote: You must use different views, it doesn't make sense to have the same view, it's going to confuseSlidingDrawer:) On Thu, Apr 30, 2009 at 2:38 PM, Sheepz eladk...@gmail.com wrote: yeah, i figured that might be it, but even after this fix: SlidingDrawerandroid:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView01 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer i still get the same error - i'm gonna try using diffrent views for the content and the handle brb :) On Apr 30, 5:32 pm, Romain Guy romain...@google.com wrote: There is a bug indeed, the exception message says the handle is missing, but the content is missing. Check out the javadoc. I'll fix the exception message. On Thu, Apr 30, 2009 at 2:26 PM, Sheepz eladk...@gmail.com wrote: okay, i might be missing something, the reason i think that this is a bug is that if you use the supplied tool, and cannot avoid getting an exception - it's a bug... i don't see any way around it - the way to create this widget is:
[android-developers] Re: SlidingDrawer
Hi All, I am able to do that.. But i can not place the SlidingDrawer at the top. It is coming bottom/right. Please help me in this regards... Thanks On May 12, 9:51 am, JITU meet2...@gmail.com wrote: Hi All, I am new to android.I need some help regarding Slidingdrawer which is included with SDK 1.5. I want to implement this feature in my application, i did not get it anywhere. Please provide me the sample-code (Java and XML). Objective: i want to put two icons (Clickable i.e buttons) with in the sliding-drawer. Thanks. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer issue #1?
As I said before I have the same issue as Sheepz. It works fine in runtime, but in layout editor in eclipse there is Exception. For me it looks like a bug in plugin. And for forthcoming questions: I am using latest SDK (1.5) and proper eclipse plugin. On May 6, 1:34 am, Sheepz eladk...@gmail.com wrote: if you mean 1.5, yes i am, i have also updated the editors for eclipse as described in the upgrade sdk page. On May 5, 7:06 pm, dan raaka danra...@gmail.com wrote: are you using the latest version of SDK ? On Tue, May 5, 2009 at 4:04 PM, Sheepz eladk...@gmail.com wrote: I took a look at the api http://developer.android.com/reference/android/widget/SlidingDrawer.html and copied their example to a clean sandbox project this is the code: [beginquote] ?xml version=1.0 encoding=utf-8? LinearLayout xmlns:android=http://schemas.android.com/apk/res/ android android:orientation=vertical android:layout_width=fill_parent android:layout_height=fill_parent SlidingDrawer android:id=@+id/drawer android:layout_width=fill_parent android:layout_height=fill_parent android:handle=@+id/handle android:content=@+id/content ImageView android:id=@id/handle android:layout_width=88dip android:layout_height=44dip android:src=@drawable/icon / GridView android:id=@id/content android:layout_width=fill_parent android:layout_height=fill_parent /GridView /SlidingDrawer /LinearLayout [endquote] this gives out the exception in eclipse, but it does run well... does anybody know why this is happening? can anyone else confirm this is happening on their environment? Thanks, Sh On May 1, 11:29 pm, Sheepz eladk...@gmail.com wrote: anyone found a solution? On May 1, 10:03 am, cannehal tomasz.l...@gmail.com wrote: I tkink I have the same issue. For handle I have ImageView and for content I am using LinearLayout with some views inside of it. There is probably problem with eclipse plugin because in runtime it works fine. On May 1, 7:01 am, Sheepz eladk...@gmail.com wrote: anyone else found something here? On Apr 30, 5:43 pm, Sheepz eladk...@gmail.com wrote: okay, that didnt work :( SlidingDrawerandroid:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView02 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/back2/ ImageView ImageView android:id=@id/ImageView02 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer still getting the same message in the ADT only now when launching the app, it simply stalls half drawn instead of giving an error message saying the application threw an exception... On Apr 30, 5:40 pm, Romain Guy romain...@google.com wrote: You must use different views, it doesn't make sense to have the same view, it's going to confuseSlidingDrawer:) On Thu, Apr 30, 2009 at 2:38 PM, Sheepz eladk...@gmail.com wrote: yeah, i figured that might be it, but even after this fix: SlidingDrawerandroid:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView01 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer i still get the same error - i'm gonna try using diffrent views for the content and the handle brb :) On Apr 30, 5:32 pm, Romain Guy romain...@google.com wrote: There is a bug indeed, the exception message says the handle is missing, but the content is missing. Check out the javadoc. I'll fix the exception message. On Thu, Apr 30, 2009 at 2:26 PM, Sheepz eladk...@gmail.com wrote: okay, i might be missing something, the reason i think that this is a bug is that if you use the supplied tool, and cannot avoid getting an exception - it's a bug... i don't see any way around it - the way to create this widget is: a) create widget b) get exception c) fix error d) populate it with the values you want by the way, i still havent gotten it to work on my app - here's the code: TableLayout LinearLayout ...
[android-developers] Re: SlidingDrawer issue #1?
I took a look at the api http://developer.android.com/reference/android/widget/SlidingDrawer.html and copied their example to a clean sandbox project this is the code: [beginquote] ?xml version=1.0 encoding=utf-8? LinearLayout xmlns:android=http://schemas.android.com/apk/res/ android android:orientation=vertical android:layout_width=fill_parent android:layout_height=fill_parent SlidingDrawer android:id=@+id/drawer android:layout_width=fill_parent android:layout_height=fill_parent android:handle=@+id/handle android:content=@+id/content ImageView android:id=@id/handle android:layout_width=88dip android:layout_height=44dip android:src=@drawable/icon / GridView android:id=@id/content android:layout_width=fill_parent android:layout_height=fill_parent /GridView /SlidingDrawer /LinearLayout [endquote] this gives out the exception in eclipse, but it does run well... does anybody know why this is happening? can anyone else confirm this is happening on their environment? Thanks, Sh On May 1, 11:29 pm, Sheepz eladk...@gmail.com wrote: anyone found a solution? On May 1, 10:03 am, cannehal tomasz.l...@gmail.com wrote: I tkink I have the same issue. For handle I have ImageView and for content I am using LinearLayout with some views inside of it. There is probably problem with eclipse plugin because in runtime it works fine. On May 1, 7:01 am, Sheepz eladk...@gmail.com wrote: anyone else found something here? On Apr 30, 5:43 pm, Sheepz eladk...@gmail.com wrote: okay, that didnt work :( SlidingDrawerandroid:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView02 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/back2/ ImageView ImageView android:id=@id/ImageView02 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer still getting the same message in the ADT only now when launching the app, it simply stalls half drawn instead of giving an error message saying the application threw an exception... On Apr 30, 5:40 pm, Romain Guy romain...@google.com wrote: You must use different views, it doesn't make sense to have the same view, it's going to confuseSlidingDrawer:) On Thu, Apr 30, 2009 at 2:38 PM, Sheepz eladk...@gmail.com wrote: yeah, i figured that might be it, but even after this fix: SlidingDrawerandroid:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView01 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer i still get the same error - i'm gonna try using diffrent views for the content and the handle brb :) On Apr 30, 5:32 pm, Romain Guy romain...@google.com wrote: There is a bug indeed, the exception message says the handle is missing, but the content is missing. Check out the javadoc. I'll fix the exception message. On Thu, Apr 30, 2009 at 2:26 PM, Sheepz eladk...@gmail.com wrote: okay, i might be missing something, the reason i think that this is a bug is that if you use the supplied tool, and cannot avoid getting an exception - it's a bug... i don't see any way around it - the way to create this widget is: a) create widget b) get exception c) fix error d) populate it with the values you want by the way, i still havent gotten it to work on my app - here's the code: TableLayout LinearLayout ... /LinearLayout SlidingDrawerandroid:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ ImageView01 ImageView android:id=@+id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer /TableLayout I guess i'm doing something wrong here - but i'm used to the whole hierarchical way of things - why is this different in it's implementation? Thanks for the quick answers btw! Sh. (p.s. if you want to see the rest of the layout, it's available at: http://code.google.com/p/bestcardgameever-android/) On Apr 30, 5:21 pm, Romain Guy romain...@google.com wrote: It *needs* a handle. It's not a bug, it's
[android-developers] Re: SlidingDrawer issue #1?
are you using the latest version of SDK ? On Tue, May 5, 2009 at 4:04 PM, Sheepz eladk...@gmail.com wrote: I took a look at the api http://developer.android.com/reference/android/widget/SlidingDrawer.html and copied their example to a clean sandbox project this is the code: [beginquote] ?xml version=1.0 encoding=utf-8? LinearLayout xmlns:android=http://schemas.android.com/apk/res/ android android:orientation=vertical android:layout_width=fill_parent android:layout_height=fill_parent SlidingDrawer android:id=@+id/drawer android:layout_width=fill_parent android:layout_height=fill_parent android:handle=@+id/handle android:content=@+id/content ImageView android:id=@id/handle android:layout_width=88dip android:layout_height=44dip android:src=@drawable/icon / GridView android:id=@id/content android:layout_width=fill_parent android:layout_height=fill_parent /GridView /SlidingDrawer /LinearLayout [endquote] this gives out the exception in eclipse, but it does run well... does anybody know why this is happening? can anyone else confirm this is happening on their environment? Thanks, Sh On May 1, 11:29 pm, Sheepz eladk...@gmail.com wrote: anyone found a solution? On May 1, 10:03 am, cannehal tomasz.l...@gmail.com wrote: I tkink I have the same issue. For handle I have ImageView and for content I am using LinearLayout with some views inside of it. There is probably problem with eclipse plugin because in runtime it works fine. On May 1, 7:01 am, Sheepz eladk...@gmail.com wrote: anyone else found something here? On Apr 30, 5:43 pm, Sheepz eladk...@gmail.com wrote: okay, that didnt work :( SlidingDrawerandroid:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView02 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/back2/ ImageView ImageView android:id=@id/ImageView02 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer still getting the same message in the ADT only now when launching the app, it simply stalls half drawn instead of giving an error message saying the application threw an exception... On Apr 30, 5:40 pm, Romain Guy romain...@google.com wrote: You must use different views, it doesn't make sense to have the same view, it's going to confuseSlidingDrawer:) On Thu, Apr 30, 2009 at 2:38 PM, Sheepz eladk...@gmail.com wrote: yeah, i figured that might be it, but even after this fix: SlidingDrawerandroid:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView01 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer i still get the same error - i'm gonna try using diffrent views for the content and the handle brb :) On Apr 30, 5:32 pm, Romain Guy romain...@google.com wrote: There is a bug indeed, the exception message says the handle is missing, but the content is missing. Check out the javadoc. I'll fix the exception message. On Thu, Apr 30, 2009 at 2:26 PM, Sheepz eladk...@gmail.com wrote: okay, i might be missing something, the reason i think that this is a bug is that if you use the supplied tool, and cannot avoid getting an exception - it's a bug... i don't see any way around it - the way to create this widget is: a) create widget b) get exception c) fix error d) populate it with the values you want by the way, i still havent gotten it to work on my app - here's the code: TableLayout LinearLayout ... /LinearLayout SlidingDrawerandroid:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ ImageView01 ImageView android:id=@+id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer /TableLayout I guess i'm doing something wrong here - but i'm used to the whole hierarchical way of things - why is this different in it's implementation? Thanks for the quick answers btw! Sh. (p.s. if you want to see the rest of the layout, it's
[android-developers] Re: SlidingDrawer issue #1?
if you mean 1.5, yes i am, i have also updated the editors for eclipse as described in the upgrade sdk page. On May 5, 7:06 pm, dan raaka danra...@gmail.com wrote: are you using the latest version of SDK ? On Tue, May 5, 2009 at 4:04 PM, Sheepz eladk...@gmail.com wrote: I took a look at the api http://developer.android.com/reference/android/widget/SlidingDrawer.html and copied their example to a clean sandbox project this is the code: [beginquote] ?xml version=1.0 encoding=utf-8? LinearLayout xmlns:android=http://schemas.android.com/apk/res/ android android:orientation=vertical android:layout_width=fill_parent android:layout_height=fill_parent SlidingDrawer android:id=@+id/drawer android:layout_width=fill_parent android:layout_height=fill_parent android:handle=@+id/handle android:content=@+id/content ImageView android:id=@id/handle android:layout_width=88dip android:layout_height=44dip android:src=@drawable/icon / GridView android:id=@id/content android:layout_width=fill_parent android:layout_height=fill_parent /GridView /SlidingDrawer /LinearLayout [endquote] this gives out the exception in eclipse, but it does run well... does anybody know why this is happening? can anyone else confirm this is happening on their environment? Thanks, Sh On May 1, 11:29 pm, Sheepz eladk...@gmail.com wrote: anyone found a solution? On May 1, 10:03 am, cannehal tomasz.l...@gmail.com wrote: I tkink I have the same issue. For handle I have ImageView and for content I am using LinearLayout with some views inside of it. There is probably problem with eclipse plugin because in runtime it works fine. On May 1, 7:01 am, Sheepz eladk...@gmail.com wrote: anyone else found something here? On Apr 30, 5:43 pm, Sheepz eladk...@gmail.com wrote: okay, that didnt work :( SlidingDrawerandroid:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView02 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/back2/ ImageView ImageView android:id=@id/ImageView02 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer still getting the same message in the ADT only now when launching the app, it simply stalls half drawn instead of giving an error message saying the application threw an exception... On Apr 30, 5:40 pm, Romain Guy romain...@google.com wrote: You must use different views, it doesn't make sense to have the same view, it's going to confuseSlidingDrawer:) On Thu, Apr 30, 2009 at 2:38 PM, Sheepz eladk...@gmail.com wrote: yeah, i figured that might be it, but even after this fix: SlidingDrawerandroid:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView01 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer i still get the same error - i'm gonna try using diffrent views for the content and the handle brb :) On Apr 30, 5:32 pm, Romain Guy romain...@google.com wrote: There is a bug indeed, the exception message says the handle is missing, but the content is missing. Check out the javadoc. I'll fix the exception message. On Thu, Apr 30, 2009 at 2:26 PM, Sheepz eladk...@gmail.com wrote: okay, i might be missing something, the reason i think that this is a bug is that if you use the supplied tool, and cannot avoid getting an exception - it's a bug... i don't see any way around it - the way to create this widget is: a) create widget b) get exception c) fix error d) populate it with the values you want by the way, i still havent gotten it to work on my app - here's the code: TableLayout LinearLayout ... /LinearLayout SlidingDrawerandroid:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ ImageView01 ImageView android:id=@+id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer /TableLayout I guess i'm doing
[android-developers] Re: SlidingDrawer issue #1?
take a look at the Launcher source code in the open source ./packages/app/Launcher That should serve as a good example as to how to use it .. -Dan On Fri, May 1, 2009 at 8:29 PM, Sheepz eladk...@gmail.com wrote: anyone found a solution? On May 1, 10:03 am, cannehal tomasz.l...@gmail.com wrote: I tkink I have the same issue. For handle I have ImageView and for content I am using LinearLayout with some views inside of it. There is probably problem with eclipse plugin because in runtime it works fine. On May 1, 7:01 am, Sheepz eladk...@gmail.com wrote: anyone else found something here? On Apr 30, 5:43 pm, Sheepz eladk...@gmail.com wrote: okay, that didnt work :( SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView02 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/back2/ ImageView ImageView android:id=@id/ImageView02 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer still getting the same message in the ADT only now when launching the app, it simply stalls half drawn instead of giving an error message saying the application threw an exception... On Apr 30, 5:40 pm, Romain Guy romain...@google.com wrote: You must use different views, it doesn't make sense to have the same view, it's going to confuse SlidingDrawer :) On Thu, Apr 30, 2009 at 2:38 PM, Sheepz eladk...@gmail.com wrote: yeah, i figured that might be it, but even after this fix: SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView01 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer i still get the same error - i'm gonna try using diffrent views for the content and the handle brb :) On Apr 30, 5:32 pm, Romain Guy romain...@google.com wrote: There is a bug indeed, the exception message says the handle is missing, but the content is missing. Check out the javadoc. I'll fix the exception message. On Thu, Apr 30, 2009 at 2:26 PM, Sheepz eladk...@gmail.com wrote: okay, i might be missing something, the reason i think that this is a bug is that if you use the supplied tool, and cannot avoid getting an exception - it's a bug... i don't see any way around it - the way to create this widget is: a) create widget b) get exception c) fix error d) populate it with the values you want by the way, i still havent gotten it to work on my app - here's the code: TableLayout LinearLayout ... /LinearLayout SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ ImageView01 ImageView android:id=@+id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer /TableLayout I guess i'm doing something wrong here - but i'm used to the whole hierarchical way of things - why is this different in it's implementation? Thanks for the quick answers btw! Sh. (p.s. if you want to see the rest of the layout, it's available at: http://code.google.com/p/bestcardgameever-android/) On Apr 30, 5:21 pm, Romain Guy romain...@google.com wrote: It *needs* a handle. It's not a bug, it's a requirement to make the widget work. On Thu, Apr 30, 2009 at 2:16 PM, Sheepz eladk...@gmail.com wrote: so you mean i have to put some content in it and only then it will be visilble? even if this is true, it's still a bug - albeit with a much lower severity... i'll check it out and report back in a few. On Apr 30, 5:10 pm, Romain Guy romain...@google.com wrote: Do what the exception says: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. You need to define the widget to use as the handle of the drawer. On Thu, Apr 30, 2009 at 2:02 PM, Sheepz eladk...@gmail.com wrote: when adding a slidingDrawer object to my application, i got this error when trying to display it on the main.xml layout view i used that view to create it as the bottommost component, and immediatly got this
[android-developers] Re: SlidingDrawer issue #1?
I tkink I have the same issue. For handle I have ImageView and for content I am using LinearLayout with some views inside of it. There is probably problem with eclipse plugin because in runtime it works fine. On May 1, 7:01 am, Sheepz eladk...@gmail.com wrote: anyone else found something here? On Apr 30, 5:43 pm, Sheepz eladk...@gmail.com wrote: okay, that didnt work :( SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView02 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/back2/ ImageView ImageView android:id=@id/ImageView02 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer still getting the same message in the ADT only now when launching the app, it simply stalls half drawn instead of giving an error message saying the application threw an exception... On Apr 30, 5:40 pm, Romain Guy romain...@google.com wrote: You must use different views, it doesn't make sense to have the same view, it's going to confuse SlidingDrawer :) On Thu, Apr 30, 2009 at 2:38 PM, Sheepz eladk...@gmail.com wrote: yeah, i figured that might be it, but even after this fix: SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView01 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer i still get the same error - i'm gonna try using diffrent views for the content and the handle brb :) On Apr 30, 5:32 pm, Romain Guy romain...@google.com wrote: There is a bug indeed, the exception message says the handle is missing, but the content is missing. Check out the javadoc. I'll fix the exception message. On Thu, Apr 30, 2009 at 2:26 PM, Sheepz eladk...@gmail.com wrote: okay, i might be missing something, the reason i think that this is a bug is that if you use the supplied tool, and cannot avoid getting an exception - it's a bug... i don't see any way around it - the way to create this widget is: a) create widget b) get exception c) fix error d) populate it with the values you want by the way, i still havent gotten it to work on my app - here's the code: TableLayout LinearLayout ... /LinearLayout SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ ImageView01 ImageView android:id=@+id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer /TableLayout I guess i'm doing something wrong here - but i'm used to the whole hierarchical way of things - why is this different in it's implementation? Thanks for the quick answers btw! Sh. (p.s. if you want to see the rest of the layout, it's available at: http://code.google.com/p/bestcardgameever-android/) On Apr 30, 5:21 pm, Romain Guy romain...@google.com wrote: It *needs* a handle. It's not a bug, it's a requirement to make the widget work. On Thu, Apr 30, 2009 at 2:16 PM, Sheepz eladk...@gmail.com wrote: so you mean i have to put some content in it and only then it will be visilble? even if this is true, it's still a bug - albeit with a much lower severity... i'll check it out and report back in a few. On Apr 30, 5:10 pm, Romain Guy romain...@google.com wrote: Do what the exception says: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. You need to define the widget to use as the handle of the drawer. On Thu, Apr 30, 2009 at 2:02 PM, Sheepz eladk...@gmail.com wrote: when adding a slidingDrawer object to my application, i got this error when trying to display it on the main.xml layout view i used that view to create it as the bottommost component, and immediatly got this message in the console window and the layout stopped showing. here is the exception: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. at android.widget.SlidingDrawer.init(SlidingDrawer.java:203) at android.widget.SlidingDrawer.init(SlidingDrawer.java:180) at sun.reflect.NativeConstructorAccessorImpl.newInstance0 (Native
[android-developers] Re: SlidingDrawer issue #1?
I tkink I have the same issue. For handle I have ImageView and for content I am using LinearLayout with some views inside of it. There is probably problem with eclipse plugin because in runtime it works fine. On May 1, 7:01 am, Sheepz eladk...@gmail.com wrote: anyone else found something here? On Apr 30, 5:43 pm, Sheepz eladk...@gmail.com wrote: okay, that didnt work :( SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView02 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/back2/ ImageView ImageView android:id=@id/ImageView02 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer still getting the same message in the ADT only now when launching the app, it simply stalls half drawn instead of giving an error message saying the application threw an exception... On Apr 30, 5:40 pm, Romain Guy romain...@google.com wrote: You must use different views, it doesn't make sense to have the same view, it's going to confuse SlidingDrawer :) On Thu, Apr 30, 2009 at 2:38 PM, Sheepz eladk...@gmail.com wrote: yeah, i figured that might be it, but even after this fix: SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView01 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer i still get the same error - i'm gonna try using diffrent views for the content and the handle brb :) On Apr 30, 5:32 pm, Romain Guy romain...@google.com wrote: There is a bug indeed, the exception message says the handle is missing, but the content is missing. Check out the javadoc. I'll fix the exception message. On Thu, Apr 30, 2009 at 2:26 PM, Sheepz eladk...@gmail.com wrote: okay, i might be missing something, the reason i think that this is a bug is that if you use the supplied tool, and cannot avoid getting an exception - it's a bug... i don't see any way around it - the way to create this widget is: a) create widget b) get exception c) fix error d) populate it with the values you want by the way, i still havent gotten it to work on my app - here's the code: TableLayout LinearLayout ... /LinearLayout SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ ImageView01 ImageView android:id=@+id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer /TableLayout I guess i'm doing something wrong here - but i'm used to the whole hierarchical way of things - why is this different in it's implementation? Thanks for the quick answers btw! Sh. (p.s. if you want to see the rest of the layout, it's available at: http://code.google.com/p/bestcardgameever-android/) On Apr 30, 5:21 pm, Romain Guy romain...@google.com wrote: It *needs* a handle. It's not a bug, it's a requirement to make the widget work. On Thu, Apr 30, 2009 at 2:16 PM, Sheepz eladk...@gmail.com wrote: so you mean i have to put some content in it and only then it will be visilble? even if this is true, it's still a bug - albeit with a much lower severity... i'll check it out and report back in a few. On Apr 30, 5:10 pm, Romain Guy romain...@google.com wrote: Do what the exception says: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. You need to define the widget to use as the handle of the drawer. On Thu, Apr 30, 2009 at 2:02 PM, Sheepz eladk...@gmail.com wrote: when adding a slidingDrawer object to my application, i got this error when trying to display it on the main.xml layout view i used that view to create it as the bottommost component, and immediatly got this message in the console window and the layout stopped showing. here is the exception: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. at android.widget.SlidingDrawer.init(SlidingDrawer.java:203) at android.widget.SlidingDrawer.init(SlidingDrawer.java:180) at sun.reflect.NativeConstructorAccessorImpl.newInstance0 (Native
[android-developers] Re: SlidingDrawer issue #1?
anyone found a solution? On May 1, 10:03 am, cannehal tomasz.l...@gmail.com wrote: I tkink I have the same issue. For handle I have ImageView and for content I am using LinearLayout with some views inside of it. There is probably problem with eclipse plugin because in runtime it works fine. On May 1, 7:01 am, Sheepz eladk...@gmail.com wrote: anyone else found something here? On Apr 30, 5:43 pm, Sheepz eladk...@gmail.com wrote: okay, that didnt work :( SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView02 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/back2/ ImageView ImageView android:id=@id/ImageView02 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer still getting the same message in the ADT only now when launching the app, it simply stalls half drawn instead of giving an error message saying the application threw an exception... On Apr 30, 5:40 pm, Romain Guy romain...@google.com wrote: You must use different views, it doesn't make sense to have the same view, it's going to confuse SlidingDrawer :) On Thu, Apr 30, 2009 at 2:38 PM, Sheepz eladk...@gmail.com wrote: yeah, i figured that might be it, but even after this fix: SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView01 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer i still get the same error - i'm gonna try using diffrent views for the content and the handle brb :) On Apr 30, 5:32 pm, Romain Guy romain...@google.com wrote: There is a bug indeed, the exception message says the handle is missing, but the content is missing. Check out the javadoc. I'll fix the exception message. On Thu, Apr 30, 2009 at 2:26 PM, Sheepz eladk...@gmail.com wrote: okay, i might be missing something, the reason i think that this is a bug is that if you use the supplied tool, and cannot avoid getting an exception - it's a bug... i don't see any way around it - the way to create this widget is: a) create widget b) get exception c) fix error d) populate it with the values you want by the way, i still havent gotten it to work on my app - here's the code: TableLayout LinearLayout ... /LinearLayout SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ ImageView01 ImageView android:id=@+id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer /TableLayout I guess i'm doing something wrong here - but i'm used to the whole hierarchical way of things - why is this different in it's implementation? Thanks for the quick answers btw! Sh. (p.s. if you want to see the rest of the layout, it's available at: http://code.google.com/p/bestcardgameever-android/) On Apr 30, 5:21 pm, Romain Guy romain...@google.com wrote: It *needs* a handle. It's not a bug, it's a requirement to make the widget work. On Thu, Apr 30, 2009 at 2:16 PM, Sheepz eladk...@gmail.com wrote: so you mean i have to put some content in it and only then it will be visilble? even if this is true, it's still a bug - albeit with a much lower severity... i'll check it out and report back in a few. On Apr 30, 5:10 pm, Romain Guy romain...@google.com wrote: Do what the exception says: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. You need to define the widget to use as the handle of the drawer. On Thu, Apr 30, 2009 at 2:02 PM, Sheepz eladk...@gmail.com wrote: when adding a slidingDrawer object to my application, i got this error when trying to display it on the main.xml layout view i used that view to create it as the bottommost component, and immediatly got this message in the console window and the layout stopped showing. here is the exception: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. at
[android-developers] Re: SlidingDrawer throws RuntimeException in onMeasure
i forgot to mention that i take the reference code from Launcher however i didnt find SlidingDrawer doesnt call any makeMeasureSpec so neither did i but i encountered RuntimeException in my case so am i doing some wrong with SlidingDrawer? thanks On Apr 30, 3:43 pm, allstars allstars@gmail.com wrote: hi i would like to do some tests on SlidingDrawer however i always found RuntimeException when SlidingDrawer.onMeasure is called i check the code and think the exception is caused by unspecified MeasureSpec so i would like to ask how to setup the MeasureSpec in SlidingDrawer? thanks --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer issue #1?
Do what the exception says: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. You need to define the widget to use as the handle of the drawer. On Thu, Apr 30, 2009 at 2:02 PM, Sheepz eladk...@gmail.com wrote: when adding a slidingDrawer object to my application, i got this error when trying to display it on the main.xml layout view i used that view to create it as the bottommost component, and immediatly got this message in the console window and the layout stopped showing. here is the exception: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. at android.widget.SlidingDrawer.init(SlidingDrawer.java:203) at android.widget.SlidingDrawer.init(SlidingDrawer.java:180) at sun.reflect.NativeConstructorAccessorImpl.newInstance0 (Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance (Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance (Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at android.view.LayoutInflater.createView(LayoutInflater.java: 499) at android.view.BridgeInflater.onCreateView (BridgeInflater.java:77) at android.view.LayoutInflater.createViewFromTag (LayoutInflater.java: 562) at android.view.BridgeInflater.createViewFromTag (BridgeInflater.java: 122) at android.view.LayoutInflater.rInflate(LayoutInflater.java: 617) at android.view.LayoutInflater.inflate(LayoutInflater.java: 407) at android.view.LayoutInflater.inflate(LayoutInflater.java: 296) at com.android.layoutlib.bridge.Bridge.computeLayout (Bridge.java:371) at com.android.ide.eclipse.editors.layout.GraphicalLayoutEditor.computeLayout (Unknown Source) at com.android.ide.eclipse.editors.layout.GraphicalLayoutEditor.recomputeLayout (Unknown Source) at com.android.ide.eclipse.editors.layout.GraphicalLayoutEditor $2.run (Unknown Source) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java: 35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages (Synchronizer.java:133) at org.eclipse.swt.widgets.Display.runAsyncMessages (Display.java: 3800) at org.eclipse.swt.widgets.Display.readAndDispatch (Display.java:3425) at org.eclipse.ui.internal.Workbench.runEventLoop (Workbench.java: 2384) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java: 2348) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java: 2200) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495) at org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench (Workbench.java:490) at org.eclipse.ui.PlatformUI.createAndRunWorkbench (PlatformUI.java: 149) at org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run (EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication (EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start (EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run (EclipseStarter.java:386) at org.eclipse.core.runtime.adaptor.EclipseStarter.run (EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) -- 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 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer issue #1?
It *needs* a handle. It's not a bug, it's a requirement to make the widget work. On Thu, Apr 30, 2009 at 2:16 PM, Sheepz eladk...@gmail.com wrote: so you mean i have to put some content in it and only then it will be visilble? even if this is true, it's still a bug - albeit with a much lower severity... i'll check it out and report back in a few. On Apr 30, 5:10 pm, Romain Guy romain...@google.com wrote: Do what the exception says: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. You need to define the widget to use as the handle of the drawer. On Thu, Apr 30, 2009 at 2:02 PM, Sheepz eladk...@gmail.com wrote: when adding a slidingDrawer object to my application, i got this error when trying to display it on the main.xml layout view i used that view to create it as the bottommost component, and immediatly got this message in the console window and the layout stopped showing. here is the exception: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. at android.widget.SlidingDrawer.init(SlidingDrawer.java:203) at android.widget.SlidingDrawer.init(SlidingDrawer.java:180) at sun.reflect.NativeConstructorAccessorImpl.newInstance0 (Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance (Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance (Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at android.view.LayoutInflater.createView(LayoutInflater.java: 499) at android.view.BridgeInflater.onCreateView (BridgeInflater.java:77) at android.view.LayoutInflater.createViewFromTag (LayoutInflater.java: 562) at android.view.BridgeInflater.createViewFromTag (BridgeInflater.java: 122) at android.view.LayoutInflater.rInflate(LayoutInflater.java: 617) at android.view.LayoutInflater.inflate(LayoutInflater.java: 407) at android.view.LayoutInflater.inflate(LayoutInflater.java: 296) at com.android.layoutlib.bridge.Bridge.computeLayout (Bridge.java:371) at com.android.ide.eclipse.editors.layout.GraphicalLayoutEditor.computeLayout (Unknown Source) at com.android.ide.eclipse.editors.layout.GraphicalLayoutEditor.recomputeLayout (Unknown Source) at com.android.ide.eclipse.editors.layout.GraphicalLayoutEditor $2.run (Unknown Source) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java: 35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages (Synchronizer.java:133) at org.eclipse.swt.widgets.Display.runAsyncMessages (Display.java: 3800) at org.eclipse.swt.widgets.Display.readAndDispatch (Display.java:3425) at org.eclipse.ui.internal.Workbench.runEventLoop (Workbench.java: 2384) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java: 2348) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java: 2200) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495) at org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench (Workbench.java:490) at org.eclipse.ui.PlatformUI.createAndRunWorkbench (PlatformUI.java: 149) at org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run (EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication (EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start (EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run (EclipseStarter.java:386) at org.eclipse.core.runtime.adaptor.EclipseStarter.run (EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) -- 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 -- Romain Guy Android framework engineer romain...@android.com Note: please don't send private questions to me, as I don't have time to
[android-developers] Re: SlidingDrawer issue #1?
okay, i might be missing something, the reason i think that this is a bug is that if you use the supplied tool, and cannot avoid getting an exception - it's a bug... i don't see any way around it - the way to create this widget is: a) create widget b) get exception c) fix error d) populate it with the values you want by the way, i still havent gotten it to work on my app - here's the code: TableLayout LinearLayout ... /LinearLayout SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ ImageView01 ImageView android:id=@+id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer /TableLayout I guess i'm doing something wrong here - but i'm used to the whole hierarchical way of things - why is this different in it's implementation? Thanks for the quick answers btw! Sh. (p.s. if you want to see the rest of the layout, it's available at: http://code.google.com/p/bestcardgameever-android/ ) On Apr 30, 5:21 pm, Romain Guy romain...@google.com wrote: It *needs* a handle. It's not a bug, it's a requirement to make the widget work. On Thu, Apr 30, 2009 at 2:16 PM, Sheepz eladk...@gmail.com wrote: so you mean i have to put some content in it and only then it will be visilble? even if this is true, it's still a bug - albeit with a much lower severity... i'll check it out and report back in a few. On Apr 30, 5:10 pm, Romain Guy romain...@google.com wrote: Do what the exception says: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. You need to define the widget to use as the handle of the drawer. On Thu, Apr 30, 2009 at 2:02 PM, Sheepz eladk...@gmail.com wrote: when adding a slidingDrawer object to my application, i got this error when trying to display it on the main.xml layout view i used that view to create it as the bottommost component, and immediatly got this message in the console window and the layout stopped showing. here is the exception: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. at android.widget.SlidingDrawer.init(SlidingDrawer.java:203) at android.widget.SlidingDrawer.init(SlidingDrawer.java:180) at sun.reflect.NativeConstructorAccessorImpl.newInstance0 (Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance (Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance (Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at android.view.LayoutInflater.createView(LayoutInflater.java: 499) at android.view.BridgeInflater.onCreateView (BridgeInflater.java:77) at android.view.LayoutInflater.createViewFromTag (LayoutInflater.java: 562) at android.view.BridgeInflater.createViewFromTag (BridgeInflater.java: 122) at android.view.LayoutInflater.rInflate(LayoutInflater.java: 617) at android.view.LayoutInflater.inflate(LayoutInflater.java: 407) at android.view.LayoutInflater.inflate(LayoutInflater.java: 296) at com.android.layoutlib.bridge.Bridge.computeLayout (Bridge.java:371) at com.android.ide.eclipse.editors.layout.GraphicalLayoutEditor.computeLayout (Unknown Source) at com.android.ide.eclipse.editors.layout.GraphicalLayoutEditor.recomputeLayout (Unknown Source) at com.android.ide.eclipse.editors.layout.GraphicalLayoutEditor $2.run (Unknown Source) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java: 35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages (Synchronizer.java:133) at org.eclipse.swt.widgets.Display.runAsyncMessages (Display.java: 3800) at org.eclipse.swt.widgets.Display.readAndDispatch (Display.java:3425) at org.eclipse.ui.internal.Workbench.runEventLoop (Workbench.java: 2384) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java: 2348) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java: 2200) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495) at org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench (Workbench.java:490) at org.eclipse.ui.PlatformUI.createAndRunWorkbench (PlatformUI.java: 149) at org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run (EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication
[android-developers] Re: SlidingDrawer issue #1?
There is a bug indeed, the exception message says the handle is missing, but the content is missing. Check out the javadoc. I'll fix the exception message. On Thu, Apr 30, 2009 at 2:26 PM, Sheepz eladk...@gmail.com wrote: okay, i might be missing something, the reason i think that this is a bug is that if you use the supplied tool, and cannot avoid getting an exception - it's a bug... i don't see any way around it - the way to create this widget is: a) create widget b) get exception c) fix error d) populate it with the values you want by the way, i still havent gotten it to work on my app - here's the code: TableLayout LinearLayout ... /LinearLayout SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ ImageView01 ImageView android:id=@+id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer /TableLayout I guess i'm doing something wrong here - but i'm used to the whole hierarchical way of things - why is this different in it's implementation? Thanks for the quick answers btw! Sh. (p.s. if you want to see the rest of the layout, it's available at: http://code.google.com/p/bestcardgameever-android/ ) On Apr 30, 5:21 pm, Romain Guy romain...@google.com wrote: It *needs* a handle. It's not a bug, it's a requirement to make the widget work. On Thu, Apr 30, 2009 at 2:16 PM, Sheepz eladk...@gmail.com wrote: so you mean i have to put some content in it and only then it will be visilble? even if this is true, it's still a bug - albeit with a much lower severity... i'll check it out and report back in a few. On Apr 30, 5:10 pm, Romain Guy romain...@google.com wrote: Do what the exception says: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. You need to define the widget to use as the handle of the drawer. On Thu, Apr 30, 2009 at 2:02 PM, Sheepz eladk...@gmail.com wrote: when adding a slidingDrawer object to my application, i got this error when trying to display it on the main.xml layout view i used that view to create it as the bottommost component, and immediatly got this message in the console window and the layout stopped showing. here is the exception: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. at android.widget.SlidingDrawer.init(SlidingDrawer.java:203) at android.widget.SlidingDrawer.init(SlidingDrawer.java:180) at sun.reflect.NativeConstructorAccessorImpl.newInstance0 (Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance (Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance (Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at android.view.LayoutInflater.createView(LayoutInflater.java: 499) at android.view.BridgeInflater.onCreateView (BridgeInflater.java:77) at android.view.LayoutInflater.createViewFromTag (LayoutInflater.java: 562) at android.view.BridgeInflater.createViewFromTag (BridgeInflater.java: 122) at android.view.LayoutInflater.rInflate(LayoutInflater.java: 617) at android.view.LayoutInflater.inflate(LayoutInflater.java: 407) at android.view.LayoutInflater.inflate(LayoutInflater.java: 296) at com.android.layoutlib.bridge.Bridge.computeLayout (Bridge.java:371) at com.android.ide.eclipse.editors.layout.GraphicalLayoutEditor.computeLayout (Unknown Source) at com.android.ide.eclipse.editors.layout.GraphicalLayoutEditor.recomputeLayout (Unknown Source) at com.android.ide.eclipse.editors.layout.GraphicalLayoutEditor $2.run (Unknown Source) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java: 35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages (Synchronizer.java:133) at org.eclipse.swt.widgets.Display.runAsyncMessages (Display.java: 3800) at org.eclipse.swt.widgets.Display.readAndDispatch (Display.java:3425) at org.eclipse.ui.internal.Workbench.runEventLoop (Workbench.java: 2384) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java: 2348) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java: 2200) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495) at org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench (Workbench.java:490) at org.eclipse.ui.PlatformUI.createAndRunWorkbench (PlatformUI.java: 149) at
[android-developers] Re: SlidingDrawer issue #1?
okay, that didnt work :( SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView02 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/back2/ ImageView ImageView android:id=@id/ImageView02 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer still getting the same message in the ADT only now when launching the app, it simply stalls half drawn instead of giving an error message saying the application threw an exception... On Apr 30, 5:40 pm, Romain Guy romain...@google.com wrote: You must use different views, it doesn't make sense to have the same view, it's going to confuse SlidingDrawer :) On Thu, Apr 30, 2009 at 2:38 PM, Sheepz eladk...@gmail.com wrote: yeah, i figured that might be it, but even after this fix: SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView01 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer i still get the same error - i'm gonna try using diffrent views for the content and the handle brb :) On Apr 30, 5:32 pm, Romain Guy romain...@google.com wrote: There is a bug indeed, the exception message says the handle is missing, but the content is missing. Check out the javadoc. I'll fix the exception message. On Thu, Apr 30, 2009 at 2:26 PM, Sheepz eladk...@gmail.com wrote: okay, i might be missing something, the reason i think that this is a bug is that if you use the supplied tool, and cannot avoid getting an exception - it's a bug... i don't see any way around it - the way to create this widget is: a) create widget b) get exception c) fix error d) populate it with the values you want by the way, i still havent gotten it to work on my app - here's the code: TableLayout LinearLayout ... /LinearLayout SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ ImageView01 ImageView android:id=@+id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer /TableLayout I guess i'm doing something wrong here - but i'm used to the whole hierarchical way of things - why is this different in it's implementation? Thanks for the quick answers btw! Sh. (p.s. if you want to see the rest of the layout, it's available at: http://code.google.com/p/bestcardgameever-android/) On Apr 30, 5:21 pm, Romain Guy romain...@google.com wrote: It *needs* a handle. It's not a bug, it's a requirement to make the widget work. On Thu, Apr 30, 2009 at 2:16 PM, Sheepz eladk...@gmail.com wrote: so you mean i have to put some content in it and only then it will be visilble? even if this is true, it's still a bug - albeit with a much lower severity... i'll check it out and report back in a few. On Apr 30, 5:10 pm, Romain Guy romain...@google.com wrote: Do what the exception says: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. You need to define the widget to use as the handle of the drawer. On Thu, Apr 30, 2009 at 2:02 PM, Sheepz eladk...@gmail.com wrote: when adding a slidingDrawer object to my application, i got this error when trying to display it on the main.xml layout view i used that view to create it as the bottommost component, and immediatly got this message in the console window and the layout stopped showing. here is the exception: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. at android.widget.SlidingDrawer.init(SlidingDrawer.java:203) at android.widget.SlidingDrawer.init(SlidingDrawer.java:180) at sun.reflect.NativeConstructorAccessorImpl.newInstance0 (Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance (Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance (Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at android.view.LayoutInflater.createView(LayoutInflater.java: 499) at android.view.BridgeInflater.onCreateView (BridgeInflater.java:77) at android.view.LayoutInflater.createViewFromTag (LayoutInflater.java: 562) at
[android-developers] Re: SlidingDrawer issue #1?
anyone else found something here? On Apr 30, 5:43 pm, Sheepz eladk...@gmail.com wrote: okay, that didnt work :( SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView02 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/back2/ ImageView ImageView android:id=@id/ImageView02 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer still getting the same message in the ADT only now when launching the app, it simply stalls half drawn instead of giving an error message saying the application threw an exception... On Apr 30, 5:40 pm, Romain Guy romain...@google.com wrote: You must use different views, it doesn't make sense to have the same view, it's going to confuse SlidingDrawer :) On Thu, Apr 30, 2009 at 2:38 PM, Sheepz eladk...@gmail.com wrote: yeah, i figured that might be it, but even after this fix: SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ImageView01 android:content=@+id/ImageView01 ImageView android:id=@id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer i still get the same error - i'm gonna try using diffrent views for the content and the handle brb :) On Apr 30, 5:32 pm, Romain Guy romain...@google.com wrote: There is a bug indeed, the exception message says the handle is missing, but the content is missing. Check out the javadoc. I'll fix the exception message. On Thu, Apr 30, 2009 at 2:26 PM, Sheepz eladk...@gmail.com wrote: okay, i might be missing something, the reason i think that this is a bug is that if you use the supplied tool, and cannot avoid getting an exception - it's a bug... i don't see any way around it - the way to create this widget is: a) create widget b) get exception c) fix error d) populate it with the values you want by the way, i still havent gotten it to work on my app - here's the code: TableLayout LinearLayout ... /LinearLayout SlidingDrawer android:id=@+id/SlidingDrawer01 android:layout_width=wrap_content android:layout_height=wrap_content android:handle=@+id/ ImageView01 ImageView android:id=@+id/ImageView01 android:layout_width=wrap_content android:layout_height=wrap_content android:src=@drawable/ahh/ ImageView /SlidingDrawer /TableLayout I guess i'm doing something wrong here - but i'm used to the whole hierarchical way of things - why is this different in it's implementation? Thanks for the quick answers btw! Sh. (p.s. if you want to see the rest of the layout, it's available at: http://code.google.com/p/bestcardgameever-android/) On Apr 30, 5:21 pm, Romain Guy romain...@google.com wrote: It *needs* a handle. It's not a bug, it's a requirement to make the widget work. On Thu, Apr 30, 2009 at 2:16 PM, Sheepz eladk...@gmail.com wrote: so you mean i have to put some content in it and only then it will be visilble? even if this is true, it's still a bug - albeit with a much lower severity... i'll check it out and report back in a few. On Apr 30, 5:10 pm, Romain Guy romain...@google.com wrote: Do what the exception says: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. You need to define the widget to use as the handle of the drawer. On Thu, Apr 30, 2009 at 2:02 PM, Sheepz eladk...@gmail.com wrote: when adding a slidingDrawer object to my application, i got this error when trying to display it on the main.xml layout view i used that view to create it as the bottommost component, and immediatly got this message in the console window and the layout stopped showing. here is the exception: java.lang.IllegalArgumentException: The handle attribute is required and must refer to a valid child. at android.widget.SlidingDrawer.init(SlidingDrawer.java:203) at android.widget.SlidingDrawer.init(SlidingDrawer.java:180) at sun.reflect.NativeConstructorAccessorImpl.newInstance0 (Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance (Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance (Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at android.view.LayoutInflater.createView(LayoutInflater.java: 499)
[android-developers] Re: SlidingDrawer not working with RC33
I'd welcome that too. For some reason my app's Listview-based menu according to recent user reports breaks (crashes) on some phones, but I cannot get it to break on my vanilla dev phone 1 (thus making it very hard to track down and fix the problem). I'm not using any private classes AFAIK, but any supplemental compliance checking for proper usage of APIs could prove helpful in reducing the chances of inadvertently running into firmware dependencies. Thanks On Feb 8, 11:10 am, Al Sutton a...@funkyandroid.com wrote: Looks like we're on the same page :). Just PLEASE make this a public API checker (possibly as part of the SDK). I'd happily include the check into AndAppStore, and I'm sure Shane would be interested in putting into SlideME as well. Al. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
If you are not using reflection or not trying to use any non android.* API or non android.R.* resource, then a compatibility check would not help. The SDK *is* the compatibility check (except, unfortunately for the case discussed in this thread before.) On Tue, Feb 17, 2009 at 1:58 AM, blindfold seeingwithso...@gmail.com wrote: I'd welcome that too. For some reason my app's Listview-based menu according to recent user reports breaks (crashes) on some phones, but I cannot get it to break on my vanilla dev phone 1 (thus making it very hard to track down and fix the problem). I'm not using any private classes AFAIK, but any supplemental compliance checking for proper usage of APIs could prove helpful in reducing the chances of inadvertently running into firmware dependencies. Thanks On Feb 8, 11:10 am, Al Sutton a...@funkyandroid.com wrote: Looks like we're on the same page :). Just PLEASE make this a public API checker (possibly as part of the SDK). I'd happily include the check into AndAppStore, and I'm sure Shane would be interested in putting into SlideME as well. Al. -- 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 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
Hi Dianne and anyone else who might care about this, I'm a little (ok, more than a little) disappointed regarding RC33 and the lack of communicating UI look/behavior changes to developers. The specific reason is that RC33 seems to also have one more UI change - Dialog titles can't be longer than 2 lines. The change itself is reasonable and I'm fine with it but the problem is that I'm finding out about this change by an email from a US user of my app who said he can't read the text of some Dialogs. For him (and all other US users who have received the update), my app suddenly broke after he received the OTA update. And that's not because I used JNI, undocumented code or internal classes that you all seem to be very worried about :) In my opinion it broke because: a) I used titles that are longer than 2 lines b) a subtle change in the UI behavior in RC33 c) the failure to warn developers before this update was pushed out For this case - all I can say to the end-user is that the OTA update broke the app and he should blame Google and/or t-mobile for it. Of course I should never use dialog titles longer than one or two lines but that's not my point :) I'm not talking about this specific change. I'm complaining and whining about the lack of any warning and/or changelog and/or updated SDK BEFORE the end-users get the update and see that things are broken. Providing the changelog or SDK AFTER the update is kind of pointless since people start having problems right after they receive the update. I'm not asking for ponies here, really. Just some kind of communication with the developers about upcoming changes. Currently the app lifecycle for the user is: Download app - get OTA - broken app - wait for app update - download app update - working app - get OTA - broken app - wait for app update - download app update - working app - .. How it should be (in a perfect world): Download app - download app update - get OTA update - download app update - get OTA update -..and the app is always working for the user. Anyway - it would be nice to know beforehand if someone decides that the correct length for dialog titles is 1 line instead of 2 in a future update so I could update my apps BEFORE they break again ;) Tauno If there are actual places where you can use internal Java APIs, we definitely want to hear about them (with sample code) to fix them. So far, I am not clear if that is what is going on here, or if it is just a matter of taking advantage of the layout file to access an internal class, which as I say is outside the bounds of what I think we can protect against. That said, I don't think we can make any assurances of an application working flawlessly on a platform update even if it completely sticks to the SDK. We are certainly going to do what we can to keep things working, and definitely don't want to just break things, but: (a) The platform code -is- changing and there can be situations where some select application is relying on some behavior that has changed, which may result in some issue for it. (b) In some very rare circumstances it may be necessary to change something for larger good of the platform, for example in Cupcake applications can't modify the data roaming setting so if someone is relying on that their call will no longer do anything (though we made sure to not through an exception and just crash the app). One other example I noticed - the text on the tab buttons - in RC30 if it is longer - it wraps, in RC33 - the same text is displayed in a marquee). Is this an API change? While the tab text is probably not significant issue, it points that you really don't know about it until you get the RC33 and realize that your UI may be a bit off here and there. Yeah this was a change made for internationalization purposes, to make the tabs more flexible about the text in them so that localizing it wouldn't break the UI. While this is certainly a change in behavior, it is not clear whether this is really an API change or not. :) (Falls in my (a) category above.) This is also kind-of part of a larger issue we will all be dealing with, that as we move forward hardware vendors are going to want to customize the Android UI for their device. We need to be careful that this doesn't cause applications to break, but if you are using standard widgets you do need to do that with the expectation that you don't know -exactly- what you will get, but rather that your UI will match the UI of the rest of the device. The truth is API changes happen - sometimes they are big and obvious, sometimes small and less obvious. In my opinion the smart thing to do is to give developers the information and tools to react to the changes and update our applications as soon as possible. If you've been following along since before 1.0, you've seen the SDK updates we've done as the platform has changed. There shouldn't be anything of that magnitude any more (we
[android-developers] Re: SlidingDrawer not working with RC33
Currently the app lifecycle for the user is: Download app - get OTA - broken app - wait for app update - download app update - working app - get OTA - broken app - wait for app update - download app update - working app - .. Which is exactly why we tell developers not to use private APIs. But that's not your case and I already apologized for the lack of changelog for the current update. And you're right the SDK should also go out to developers before the update reaches the users. The good news is, it is what we want to do for Cupcake :) -- 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 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
Dianne, To finish that dreaded SlidingDrawer topic - yes the use of the SlidingDrawer was in the Layout xml file only so I guess its was a loophole that I end up using without realizing. Thanks for your comments on the rest of the issues. I think we all agree that changes in the APIs happen and will happen. All we want is an advance notice so we can proactively react to them. In my experience probably a good start is to have: 1. Good Change List 2. A single pace where Google (and probably partners) can push emulator images (or ways to build them) for the various API releases and platforms. This will be a huge help to ensure we are ready for the new releases. On Feb 9, 11:32 am, Romain Guy romain...@google.com wrote: Currently the app lifecycle for the user is: Download app - get OTA - broken app - wait for app update - download app update - working app - get OTA - broken app - wait for app update - download app update - working app - .. Which is exactly why we tell developers not to use private APIs. But that's not your case and I already apologized for the lack of changelog for the current update. And you're right the SDK should also go out to developers before the update reaches the users. The good news is, it is what we want to do for Cupcake :) -- 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 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
Romain Guy wrote: Please, please don't use private APIs, it only hurts the users :( Got to admit my local doctor rarely sees people complaining about injuries caused by private API usage, but I haven't checked with the ER yet ;). Al. -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
Maybe an API compliance test should be run as part of any app build. Does an API usage checking tool exist? and is it publicly available? Al. Jean-Baptiste Queru wrote: Even worse, it hurts the entire ecosystem, by making users believe that plaftorm upgrades have bugs when in fact the applications are broken to start with. JBQ On Sat, Feb 7, 2009 at 3:18 PM, Romain Guy romain...@google.com wrote: That means your app will break in cupcake though. Please, please don't use private APIs, it only hurts the users :( On Feb 7, 2009 1:43 PM, Stefan skyntc...@gmail.com wrote: After digging a bit around in the source code, it looks like the namespace used for the attributes of the internal widgets has changed in RC33 from xmlns:android=http://schemas.android.com/apk/res/ android to some other namespace (probably something like http://schemas.android.com/apk/res/android.intenral ??) and that caused the SlidingDrawer to not find its attributes. Well... one should never rely on internal classes, but... the SlidingDrawer is actually so useful... I am glad it will make it as an officially supported class. On Feb 7, 4:34 pm, Romain Guy romain...@google.com wrote: Even worse, SlidingDrawer will move ... On Sat, Feb 7, 2009 at 12:14 PM, Jean-Baptiste Queru j...@android.com wrote:Oh, ah, I had... On Sat, Feb 7, 2009 at 11:28 AM, Romain Guy romain...@google.com wrote:No, SlidingDraw... On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue inhttp://b.android.com/? (a plain copy-paste will do).Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that ... romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private... 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 suppo... -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
That's the whole point of the SDK. It does NOT let you use private APIs since they are stripped out of the SDK. If you compile your app against the git tree or a custom SDK, there's not much we can do. It's also up to the developers to be reasonable. On Sun, Feb 8, 2009 at 1:43 AM, Al Sutton a...@funkyandroid.com wrote: Maybe an API compliance test should be run as part of any app build. Does an API usage checking tool exist? and is it publicly available? Al. Jean-Baptiste Queru wrote: Even worse, it hurts the entire ecosystem, by making users believe that plaftorm upgrades have bugs when in fact the applications are broken to start with. JBQ On Sat, Feb 7, 2009 at 3:18 PM, Romain Guy romain...@google.com wrote: That means your app will break in cupcake though. Please, please don't use private APIs, it only hurts the users :( On Feb 7, 2009 1:43 PM, Stefan skyntc...@gmail.com wrote: After digging a bit around in the source code, it looks like the namespace used for the attributes of the internal widgets has changed in RC33 from xmlns:android=http://schemas.android.com/apk/res/ android to some other namespace (probably something like http://schemas.android.com/apk/res/android.intenral ??) and that caused the SlidingDrawer to not find its attributes. Well... one should never rely on internal classes, but... the SlidingDrawer is actually so useful... I am glad it will make it as an officially supported class. On Feb 7, 4:34 pm, Romain Guy romain...@google.com wrote: Even worse, SlidingDrawer will move ... On Sat, Feb 7, 2009 at 12:14 PM, Jean-Baptiste Queru j...@android.com wrote:Oh, ah, I had... On Sat, Feb 7, 2009 at 11:28 AM, Romain Guy romain...@google.com wrote:No, SlidingDraw... On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue inhttp://b.android.com/? (a plain copy-paste will do).Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that ... romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private... 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 suppo... -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. -- 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 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
Is checking API usage in a apk feasible? That way problems could be picked up at distribution or installation time? Al. Romain Guy wrote: That's the whole point of the SDK. It does NOT let you use private APIs since they are stripped out of the SDK. If you compile your app against the git tree or a custom SDK, there's not much we can do. It's also up to the developers to be reasonable. On Sun, Feb 8, 2009 at 1:43 AM, Al Sutton a...@funkyandroid.com wrote: Maybe an API compliance test should be run as part of any app build. Does an API usage checking tool exist? and is it publicly available? Al. Jean-Baptiste Queru wrote: Even worse, it hurts the entire ecosystem, by making users believe that plaftorm upgrades have bugs when in fact the applications are broken to start with. JBQ On Sat, Feb 7, 2009 at 3:18 PM, Romain Guy romain...@google.com wrote: That means your app will break in cupcake though. Please, please don't use private APIs, it only hurts the users :( On Feb 7, 2009 1:43 PM, Stefan skyntc...@gmail.com wrote: After digging a bit around in the source code, it looks like the namespace used for the attributes of the internal widgets has changed in RC33 from xmlns:android=http://schemas.android.com/apk/res/ android to some other namespace (probably something like http://schemas.android.com/apk/res/android.intenral ??) and that caused the SlidingDrawer to not find its attributes. Well... one should never rely on internal classes, but... the SlidingDrawer is actually so useful... I am glad it will make it as an officially supported class. On Feb 7, 4:34 pm, Romain Guy romain...@google.com wrote: Even worse, SlidingDrawer will move ... On Sat, Feb 7, 2009 at 12:14 PM, Jean-Baptiste Queru j...@android.com wrote:Oh, ah, I had... On Sat, Feb 7, 2009 at 11:28 AM, Romain Guy romain...@google.com wrote:No, SlidingDraw... On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue inhttp://b.android.com/? (a plain copy-paste will do).Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that ... romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private... 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 suppo... -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
It would be way too costly to do it at install time (both in CPU and disk space.) We could do the check during the upload to Market but that wouldn't solve the issue with apps installed through other means (especially alternatives to Market.) I'd rather trust the developers to do the right thing. On Sun, Feb 8, 2009 at 2:02 AM, Al Sutton a...@funkyandroid.com wrote: Is checking API usage in a apk feasible? That way problems could be picked up at distribution or installation time? Al. Romain Guy wrote: That's the whole point of the SDK. It does NOT let you use private APIs since they are stripped out of the SDK. If you compile your app against the git tree or a custom SDK, there's not much we can do. It's also up to the developers to be reasonable. On Sun, Feb 8, 2009 at 1:43 AM, Al Sutton a...@funkyandroid.com wrote: Maybe an API compliance test should be run as part of any app build. Does an API usage checking tool exist? and is it publicly available? Al. Jean-Baptiste Queru wrote: Even worse, it hurts the entire ecosystem, by making users believe that plaftorm upgrades have bugs when in fact the applications are broken to start with. JBQ On Sat, Feb 7, 2009 at 3:18 PM, Romain Guy romain...@google.com wrote: That means your app will break in cupcake though. Please, please don't use private APIs, it only hurts the users :( On Feb 7, 2009 1:43 PM, Stefan skyntc...@gmail.com wrote: After digging a bit around in the source code, it looks like the namespace used for the attributes of the internal widgets has changed in RC33 from xmlns:android=http://schemas.android.com/apk/res/ android to some other namespace (probably something like http://schemas.android.com/apk/res/android.intenral ??) and that caused the SlidingDrawer to not find its attributes. Well... one should never rely on internal classes, but... the SlidingDrawer is actually so useful... I am glad it will make it as an officially supported class. On Feb 7, 4:34 pm, Romain Guy romain...@google.com wrote: Even worse, SlidingDrawer will move ... On Sat, Feb 7, 2009 at 12:14 PM, Jean-Baptiste Queru j...@android.com wrote:Oh, ah, I had... On Sat, Feb 7, 2009 at 11:28 AM, Romain Guy romain...@google.com wrote:No, SlidingDraw... On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue inhttp://b.android.com/? (a plain copy-paste will do).Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that ... romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private... 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 suppo... -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. -- 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 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
That said, it could be interesting to flag bad apps on Market and warn the user that the app he's about to download might break with a future update of the system :)) On Sun, Feb 8, 2009 at 2:06 AM, Romain Guy romain...@google.com wrote: It would be way too costly to do it at install time (both in CPU and disk space.) We could do the check during the upload to Market but that wouldn't solve the issue with apps installed through other means (especially alternatives to Market.) I'd rather trust the developers to do the right thing. On Sun, Feb 8, 2009 at 2:02 AM, Al Sutton a...@funkyandroid.com wrote: Is checking API usage in a apk feasible? That way problems could be picked up at distribution or installation time? Al. Romain Guy wrote: That's the whole point of the SDK. It does NOT let you use private APIs since they are stripped out of the SDK. If you compile your app against the git tree or a custom SDK, there's not much we can do. It's also up to the developers to be reasonable. On Sun, Feb 8, 2009 at 1:43 AM, Al Sutton a...@funkyandroid.com wrote: Maybe an API compliance test should be run as part of any app build. Does an API usage checking tool exist? and is it publicly available? Al. Jean-Baptiste Queru wrote: Even worse, it hurts the entire ecosystem, by making users believe that plaftorm upgrades have bugs when in fact the applications are broken to start with. JBQ On Sat, Feb 7, 2009 at 3:18 PM, Romain Guy romain...@google.com wrote: That means your app will break in cupcake though. Please, please don't use private APIs, it only hurts the users :( On Feb 7, 2009 1:43 PM, Stefan skyntc...@gmail.com wrote: After digging a bit around in the source code, it looks like the namespace used for the attributes of the internal widgets has changed in RC33 from xmlns:android=http://schemas.android.com/apk/res/ android to some other namespace (probably something like http://schemas.android.com/apk/res/android.intenral ??) and that caused the SlidingDrawer to not find its attributes. Well... one should never rely on internal classes, but... the SlidingDrawer is actually so useful... I am glad it will make it as an officially supported class. On Feb 7, 4:34 pm, Romain Guy romain...@google.com wrote: Even worse, SlidingDrawer will move ... On Sat, Feb 7, 2009 at 12:14 PM, Jean-Baptiste Queru j...@android.com wrote:Oh, ah, I had... On Sat, Feb 7, 2009 at 11:28 AM, Romain Guy romain...@google.com wrote:No, SlidingDraw... On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue inhttp://b.android.com/? (a plain copy-paste will do).Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that ... romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private... 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 suppo... -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. -- 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 -- 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 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
I'd rather trust the developers to do the right thing. That's probably how Microsoft felt about Windows developers before the first virus came along. With APK API checking at point of distribution (AndAppStore, Market, SlideME, etc.), we could cover most user installs. I fully agree that installing from a developers site bypasses this, but once of the value add features distribution channels could add is ensuring that apks are future-proofed in terms of APIs. Al. Romain Guy wrote: It would be way too costly to do it at install time (both in CPU and disk space.) We could do the check during the upload to Market but that wouldn't solve the issue with apps installed through other means (especially alternatives to Market.) I'd rather trust the developers to do the right thing. On Sun, Feb 8, 2009 at 2:02 AM, Al Sutton a...@funkyandroid.com wrote: Is checking API usage in a apk feasible? That way problems could be picked up at distribution or installation time? Al. Romain Guy wrote: That's the whole point of the SDK. It does NOT let you use private APIs since they are stripped out of the SDK. If you compile your app against the git tree or a custom SDK, there's not much we can do. It's also up to the developers to be reasonable. On Sun, Feb 8, 2009 at 1:43 AM, Al Sutton a...@funkyandroid.com wrote: Maybe an API compliance test should be run as part of any app build. Does an API usage checking tool exist? and is it publicly available? Al. Jean-Baptiste Queru wrote: Even worse, it hurts the entire ecosystem, by making users believe that plaftorm upgrades have bugs when in fact the applications are broken to start with. JBQ On Sat, Feb 7, 2009 at 3:18 PM, Romain Guy romain...@google.com wrote: That means your app will break in cupcake though. Please, please don't use private APIs, it only hurts the users :( On Feb 7, 2009 1:43 PM, Stefan skyntc...@gmail.com wrote: After digging a bit around in the source code, it looks like the namespace used for the attributes of the internal widgets has changed in RC33 from xmlns:android=http://schemas.android.com/apk/res/ android to some other namespace (probably something like http://schemas.android.com/apk/res/android.intenral ??) and that caused the SlidingDrawer to not find its attributes. Well... one should never rely on internal classes, but... the SlidingDrawer is actually so useful... I am glad it will make it as an officially supported class. On Feb 7, 4:34 pm, Romain Guy romain...@google.com wrote: Even worse, SlidingDrawer will move ... On Sat, Feb 7, 2009 at 12:14 PM, Jean-Baptiste Queru j...@android.com wrote:Oh, ah, I had... On Sat, Feb 7, 2009 at 11:28 AM, Romain Guy romain...@google.com wrote:No, SlidingDraw... On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue inhttp://b.android.com/? (a plain copy-paste will do).Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that ... romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private... 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 suppo... -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to
[android-developers] Re: SlidingDrawer not working with RC33
I'm not sure if it should be part of the sdk. any app created with the sdk already would pass this check. It should more be a tool built into the normal make process so you get warnings like you get right now if you change the api. Additionally it could notify the developer and maybe show him a link with FAQs about internal api usage, or jni, or whatever evil was detected in the app. On Sun, Feb 8, 2009 at 11:10 AM, Al Sutton a...@funkyandroid.com wrote: Looks like we're on the same page :). Just PLEASE make this a public API checker (possibly as part of the SDK). I'd happily include the check into AndAppStore, and I'm sure Shane would be interested in putting into SlideME as well. Al. Romain Guy wrote: That said, it could be interesting to flag bad apps on Market and warn the user that the app he's about to download might break with a future update of the system :)) On Sun, Feb 8, 2009 at 2:06 AM, Romain Guy romain...@google.com wrote: It would be way too costly to do it at install time (both in CPU and disk space.) We could do the check during the upload to Market but that wouldn't solve the issue with apps installed through other means (especially alternatives to Market.) I'd rather trust the developers to do the right thing. On Sun, Feb 8, 2009 at 2:02 AM, Al Sutton a...@funkyandroid.com wrote: Is checking API usage in a apk feasible? That way problems could be picked up at distribution or installation time? Al. Romain Guy wrote: That's the whole point of the SDK. It does NOT let you use private APIs since they are stripped out of the SDK. If you compile your app against the git tree or a custom SDK, there's not much we can do. It's also up to the developers to be reasonable. On Sun, Feb 8, 2009 at 1:43 AM, Al Sutton a...@funkyandroid.com wrote: Maybe an API compliance test should be run as part of any app build. Does an API usage checking tool exist? and is it publicly available? Al. Jean-Baptiste Queru wrote: Even worse, it hurts the entire ecosystem, by making users believe that plaftorm upgrades have bugs when in fact the applications are broken to start with. JBQ On Sat, Feb 7, 2009 at 3:18 PM, Romain Guy romain...@google.com wrote: That means your app will break in cupcake though. Please, please don't use private APIs, it only hurts the users :( On Feb 7, 2009 1:43 PM, Stefan skyntc...@gmail.com wrote: After digging a bit around in the source code, it looks like the namespace used for the attributes of the internal widgets has changed in RC33 from xmlns:android=http://schemas.android.com/apk/res/ android to some other namespace (probably something like http://schemas.android.com/apk/res/android.intenral ??) and that caused the SlidingDrawer to not find its attributes. Well... one should never rely on internal classes, but... the SlidingDrawer is actually so useful... I am glad it will make it as an officially supported class. On Feb 7, 4:34 pm, Romain Guy romain...@google.com wrote: Even worse, SlidingDrawer will move ... On Sat, Feb 7, 2009 at 12:14 PM, Jean-Baptiste Queru j...@android.com wrote:Oh, ah, I had... On Sat, Feb 7, 2009 at 11:28 AM, Romain Guy romain...@google.com wrote:No, SlidingDraw... On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue inhttp://b.android.com/? (a plain copy-paste will do).Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that ... romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private... 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 suppo... -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. -- 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 -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City
[android-developers] Re: SlidingDrawer not working with RC33
I agree it's not necessary if you're building apps with the SDK, but I see it's primary usage as being by developers wanting to check an apks' compliance level and its' results would be firmly tied to the android version and thus the SDK version, so an API checker from the 1.0 SDK may generate errors for cupcake apps, but an API checker from the cupcake SDK would pass them. Al. Urs Grob wrote: I'm not sure if it should be part of the sdk. any app created with the sdk already would pass this check. It should more be a tool built into the normal make process so you get warnings like you get right now if you change the api. Additionally it could notify the developer and maybe show him a link with FAQs about internal api usage, or jni, or whatever evil was detected in the app. On Sun, Feb 8, 2009 at 11:10 AM, Al Sutton a...@funkyandroid.com wrote: Looks like we're on the same page :). Just PLEASE make this a public API checker (possibly as part of the SDK). I'd happily include the check into AndAppStore, and I'm sure Shane would be interested in putting into SlideME as well. Al. Romain Guy wrote: That said, it could be interesting to flag bad apps on Market and warn the user that the app he's about to download might break with a future update of the system :)) On Sun, Feb 8, 2009 at 2:06 AM, Romain Guy romain...@google.com wrote: It would be way too costly to do it at install time (both in CPU and disk space.) We could do the check during the upload to Market but that wouldn't solve the issue with apps installed through other means (especially alternatives to Market.) I'd rather trust the developers to do the right thing. On Sun, Feb 8, 2009 at 2:02 AM, Al Sutton a...@funkyandroid.com wrote: Is checking API usage in a apk feasible? That way problems could be picked up at distribution or installation time? Al. Romain Guy wrote: That's the whole point of the SDK. It does NOT let you use private APIs since they are stripped out of the SDK. If you compile your app against the git tree or a custom SDK, there's not much we can do. It's also up to the developers to be reasonable. On Sun, Feb 8, 2009 at 1:43 AM, Al Sutton a...@funkyandroid.com wrote: Maybe an API compliance test should be run as part of any app build. Does an API usage checking tool exist? and is it publicly available? Al. Jean-Baptiste Queru wrote: Even worse, it hurts the entire ecosystem, by making users believe that plaftorm upgrades have bugs when in fact the applications are broken to start with. JBQ On Sat, Feb 7, 2009 at 3:18 PM, Romain Guy romain...@google.com wrote: That means your app will break in cupcake though. Please, please don't use private APIs, it only hurts the users :( On Feb 7, 2009 1:43 PM, Stefan skyntc...@gmail.com wrote: After digging a bit around in the source code, it looks like the namespace used for the attributes of the internal widgets has changed in RC33 from xmlns:android=http://schemas.android.com/apk/res/ android to some other namespace (probably something like http://schemas.android.com/apk/res/android.intenral ??) and that caused the SlidingDrawer to not find its attributes. Well... one should never rely on internal classes, but... the SlidingDrawer is actually so useful... I am glad it will make it as an officially supported class. On Feb 7, 4:34 pm, Romain Guy romain...@google.com wrote: Even worse, SlidingDrawer will move ... On Sat, Feb 7, 2009 at 12:14 PM, Jean-Baptiste Queru j...@android.com wrote:Oh, ah, I had... On Sat, Feb 7, 2009 at 11:28 AM, Romain Guy romain...@google.com wrote:No, SlidingDraw... On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue inhttp://b.android.com/? (a plain copy-paste will do).Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that ... romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private... 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 suppo... -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's
[android-developers] Re: SlidingDrawer not working with RC33
Dianne, In this particular case, the SlidingDrawer class is not private, it is public but it is in the package com.android.internal.widget package. This .internal. (and the lack of official documentation on it) is the only clue you get that this class is probably not intended to be used directly. (I come from the world of Windows Mobile development where it is to a large degree a custom to rely on some undocumented APIs to do what you want to do, so that made me take that gamble, which in my case did not pay of) I actually did something similar to what you suggest - as my app was already built around it - I end up creating my own implementation for the SlidingDrawer - this way I know it will work with RC30, RC33 and probably Cupcake. I have to admit, the fact that the Android is an open source OS and we have at all access the the source code to learn and diagnose issues, is like a breath of fresh air after having to deal for many years in the proprietary Windows world. My only suggestion is that at least for the official releases RC30, RC33 etc. that are being pushed to the end users - give us a way to find what has changed in the APIs and what bugs have been fixed. I simple change list will do, or an API checking tool or whatever other means that you can think of. On Feb 7, 10:48 pm, Dianne Hackborn hack...@android.com wrote: When a new SDK is posted, there is a complete API diff and overview of the changes. However, there is very little change to the platform APIs in 1.1, so there isn't much to say about this one. I'm not sure when an SDK for it will be available. Also, out of curiosity, how did you go about using the private class? If you are actually using the SDK, you shouldn't be able to use any of the private classes, just to protect people from accidentally using things that will break on them. Finally, if there is a class like this in the internal implementation that you really want to use, just copy it out and build the copy in to your own code. That way your code won't break when the system changes. On Sat, Feb 7, 2009 at 4:10 PM, Stefan skyntc...@gmail.com wrote: Yes, I do agree that relying on private APIs is dangerous and should be avoided for all the reasons you mention. (The only reason I posted my findings is to save somebody the debugging time as it was not obvious what was the reason at first) This brings another related question. Is there a single place where we as developers can see what has changed between the public releases of the API's for example from RC30 = RC33? - (preferably both internal and external changes)? The only thing I could find is that RC33 has fixed several bugs and added several features, but nothing specific about what has changed and what bugs have been fixed. Stefan On Feb 7, 6:21 pm, Jean-Baptiste Queru j...@android.com wrote: Even worse, it hurts the entire ecosystem, by making users believe that plaftorm upgrades have bugs when in fact the applications are broken to start with. JBQ On Sat, Feb 7, 2009 at 3:18 PM, Romain Guy romain...@google.com wrote: That means your app will break in cupcake though. Please, please don't use private APIs, it only hurts the users :( On Feb 7, 2009 1:43 PM, Stefan skyntc...@gmail.com wrote: After digging a bit around in the source code, it looks like the namespace used for the attributes of the internal widgets has changed in RC33 from xmlns:android= http://schemas.android.com/apk/res/ android to some other namespace (probably something likehttp:// schemas.android.com/apk/res/android.intenral ??) and that caused the SlidingDrawer to not find its attributes. Well... one should never rely on internal classes, but... the SlidingDrawer is actually so useful... I am glad it will make it as an officially supported class. On Feb 7, 4:34 pm, Romain Guy romain...@google.com wrote: Even worse, SlidingDrawer will move ... On Sat, Feb 7, 2009 at 12:14 PM, Jean-Baptiste Queru j...@android.com wrote:Oh, ah, I had... On Sat, Feb 7, 2009 at 11:28 AM, Romain Guy romain...@google.com wrote:No, SlidingDraw... On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue inhttp://b.android.com/?(ahttp://b.android.com/?%28aplain copy-paste will do).Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that ... romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private... 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 suppo... -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. -- Dianne Hackborn Android framework
[android-developers] Re: SlidingDrawer not working with RC33
Building apps with the SDK is apparently NOT enough to insure API compliance as the example with the SlidingDrawer showed - the app was build with the latest SDK 1.0 r2 and without using reflection or any other funky access. I firmly believe that we as developers, have the most vested interest for our apps to work on the widest possible range of API versions and device types (Just wait until Android gets a candy bar style models where users rely mostly keyboard for navigation. How many of the apps available today will still work flawlessly?). If you put lots of time and effort to write your app, you want to ensure that you did not do (unknowingly) anything stupid to limit its use. Even more you want to find as soon as possible all stupid things you did and fix them before they hit the end user. I am sure we all test our apps on the emulator and the G1 device we have, but can you be absolutely sure it will work flawlessly on the next release (RC33.. Cupcake...)? One other example I noticed - the text on the tab buttons - in RC30 if it is longer - it wraps, in RC33 - the same text is displayed in a marquee). Is this an API change? While the tab text is probably not significant issue, it points that you really don't know about it until you get the RC33 and realize that your UI may be a bit off here and there. The truth is API changes happen - sometimes they are big and obvious, sometimes small and less obvious. In my opinion the smart thing to do is to give developers the information and tools to react to the changes and update our applications as soon as possible. There is probably a complementary set of tools that can help us with that: API change list, API Checking tool, Emulator images for RC30, RC33 Cupcake etc - are all ways that we can use proactively before the new platform changes are pushed to the public. On Feb 8, 5:18 am, Al Sutton a...@funkyandroid.com wrote: I agree it's not necessary if you're building apps with the SDK, but I see it's primary usage as being by developers wanting to check an apks' compliance level and its' results would be firmly tied to the android version and thus the SDK version, so an API checker from the 1.0 SDK may generate errors for cupcake apps, but an API checker from the cupcake SDK would pass them. Al. Urs Grob wrote: I'm not sure if it should be part of the sdk. any app created with the sdk already would pass this check. It should more be a tool built into the normal make process so you get warnings like you get right now if you change the api. Additionally it could notify the developer and maybe show him a link with FAQs about internal api usage, or jni, or whatever evil was detected in the app. On Sun, Feb 8, 2009 at 11:10 AM, Al Sutton a...@funkyandroid.com wrote: Looks like we're on the same page :). Just PLEASE make this a public API checker (possibly as part of the SDK). I'd happily include the check into AndAppStore, and I'm sure Shane would be interested in putting into SlideME as well. Al. Romain Guy wrote: That said, it could be interesting to flag bad apps on Market and warn the user that the app he's about to download might break with a future update of the system :)) On Sun, Feb 8, 2009 at 2:06 AM, Romain Guy romain...@google.com wrote: It would be way too costly to do it at install time (both in CPU and disk space.) We could do the check during the upload to Market but that wouldn't solve the issue with apps installed through other means (especially alternatives to Market.) I'd rather trust the developers to do the right thing. On Sun, Feb 8, 2009 at 2:02 AM, Al Sutton a...@funkyandroid.com wrote: Is checking API usage in a apk feasible? That way problems could be picked up at distribution or installation time? Al. Romain Guy wrote: That's the whole point of the SDK. It does NOT let you use private APIs since they are stripped out of the SDK. If you compile your app against the git tree or a custom SDK, there's not much we can do. It's also up to the developers to be reasonable. On Sun, Feb 8, 2009 at 1:43 AM, Al Sutton a...@funkyandroid.com wrote: Maybe an API compliance test should be run as part of any app build. Does an API usage checking tool exist? and is it publicly available? Al. Jean-Baptiste Queru wrote: Even worse, it hurts the entire ecosystem, by making users believe that plaftorm upgrades have bugs when in fact the applications are broken to start with. JBQ On Sat, Feb 7, 2009 at 3:18 PM, Romain Guy romain...@google.com wrote: That means your app will break in cupcake though. Please, please don't use private APIs, it only hurts the users :( On Feb 7, 2009 1:43 PM, Stefan skyntc...@gmail.com wrote: After digging a bit around in the source code, it looks like the namespace used for the attributes of the internal widgets has changed in RC33 from
[android-developers] Re: SlidingDrawer not working with RC33
That is a good news. May i ask a request, since you guys making a public widget , could you provide little bit flexibility where this widget ca attached to . For example there are cases when i want to attach this to the top ( currently we're using custom widget based on SlidingDrawer ). And ability to change drawable of the handle would be nice as well. On Feb 7, 3:34 pm, Romain Guy romain...@google.com wrote: Even worse, SlidingDrawer will move to android.widget in Cupcake :)) (And thus become public API.) On Sat, Feb 7, 2009 at 12:14 PM, Jean-Baptiste Queru j...@android.com wrote: Oh, ah, I hadn't seen that it was android.INTERNAL.SlidingDrawer (emphasis mine). There's no guarantee of compatibility of private APIs between versions. JBQ On Sat, Feb 7, 2009 at 11:28 AM, Romain Guy romain...@google.com wrote: No, SlidingDrawer is a private widget. It is not supported. On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue inhttp://b.android.com/? (a plain copy-paste will do). Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that android.internal.widget.SlidingDrawer widget had changed between RC30 and RC33. On RC33 it fails to inflate the layout XML complaining that: The handle attribute is required and must refer to a valid child This is the XML I am trying to inflate: com.android.internal.widget.SlidingDrawer android:id=@+id/drawer android:layout_width=fill_parent android:layout_height=wrap_content android:topOffset=5px android:bottomOffset=7px android:handle=@+id/playlistHeader android:content=@+id/playList ImageView android:id=@id/playlistHeader android:focusable=true android:clickable=true android:scaleType=center android:src=@drawable/ic_mp_current_playlist_btn android:layout_height=56dip android:layout_width=fill_parent / ListView android:id=@+id/playList android:layout_width=fill_parent android:layout_height=fill_parent android:background=@color/grid_dark_background/ /com.android.internal.widget.SlidingDrawer The XML above has both the content and the handle attribute and worked fine in RC30? Does anyone know what has changed and how to fix it? Stefan -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. -- 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 -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. -- 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 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
That is a good news. May i ask a request, since you guys making a public widget , could you provide little bit flexibility where this widget ca attached to . Won't happen for cupcake. And ability to change drawable of the handle would be nice as well. You already can. The handle is any view you want. -- 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 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
A private API does not necessarily mean the class or method has the private Java keyword on it. Actually there are many Java-public classes and methods that are part of the private APIs. Normally these are stripped from the SDK. I don't know why the internal package is still in the SDK but indeed, the internal name of the package is a good indication that this is not a public API. Again there is no need for an API checking tool in the SDK because the SDK itself *is* the API checking tool. Apparently we just let a few things slip and we need to fix them. We also perfectly agree that you should get a detailed changelog with the new SDK. Such a changelog should NOT, however, include changes about anything private and/or internal. On Sun, Feb 8, 2009 at 4:52 AM, Stefan skyntc...@gmail.com wrote: Dianne, In this particular case, the SlidingDrawer class is not private, it is public but it is in the package com.android.internal.widget package. This .internal. (and the lack of official documentation on it) is the only clue you get that this class is probably not intended to be used directly. (I come from the world of Windows Mobile development where it is to a large degree a custom to rely on some undocumented APIs to do what you want to do, so that made me take that gamble, which in my case did not pay of) I actually did something similar to what you suggest - as my app was already built around it - I end up creating my own implementation for the SlidingDrawer - this way I know it will work with RC30, RC33 and probably Cupcake. I have to admit, the fact that the Android is an open source OS and we have at all access the the source code to learn and diagnose issues, is like a breath of fresh air after having to deal for many years in the proprietary Windows world. My only suggestion is that at least for the official releases RC30, RC33 etc. that are being pushed to the end users - give us a way to find what has changed in the APIs and what bugs have been fixed. I simple change list will do, or an API checking tool or whatever other means that you can think of. On Feb 7, 10:48 pm, Dianne Hackborn hack...@android.com wrote: When a new SDK is posted, there is a complete API diff and overview of the changes. However, there is very little change to the platform APIs in 1.1, so there isn't much to say about this one. I'm not sure when an SDK for it will be available. Also, out of curiosity, how did you go about using the private class? If you are actually using the SDK, you shouldn't be able to use any of the private classes, just to protect people from accidentally using things that will break on them. Finally, if there is a class like this in the internal implementation that you really want to use, just copy it out and build the copy in to your own code. That way your code won't break when the system changes. On Sat, Feb 7, 2009 at 4:10 PM, Stefan skyntc...@gmail.com wrote: Yes, I do agree that relying on private APIs is dangerous and should be avoided for all the reasons you mention. (The only reason I posted my findings is to save somebody the debugging time as it was not obvious what was the reason at first) This brings another related question. Is there a single place where we as developers can see what has changed between the public releases of the API's for example from RC30 = RC33? - (preferably both internal and external changes)? The only thing I could find is that RC33 has fixed several bugs and added several features, but nothing specific about what has changed and what bugs have been fixed. Stefan On Feb 7, 6:21 pm, Jean-Baptiste Queru j...@android.com wrote: Even worse, it hurts the entire ecosystem, by making users believe that plaftorm upgrades have bugs when in fact the applications are broken to start with. JBQ On Sat, Feb 7, 2009 at 3:18 PM, Romain Guy romain...@google.com wrote: That means your app will break in cupcake though. Please, please don't use private APIs, it only hurts the users :( On Feb 7, 2009 1:43 PM, Stefan skyntc...@gmail.com wrote: After digging a bit around in the source code, it looks like the namespace used for the attributes of the internal widgets has changed in RC33 from xmlns:android= http://schemas.android.com/apk/res/ android to some other namespace (probably something likehttp:// schemas.android.com/apk/res/android.intenral ??) and that caused the SlidingDrawer to not find its attributes. Well... one should never rely on internal classes, but... the SlidingDrawer is actually so useful... I am glad it will make it as an officially supported class. On Feb 7, 4:34 pm, Romain Guy romain...@google.com wrote: Even worse, SlidingDrawer will move ... On Sat, Feb 7, 2009 at 12:14 PM, Jean-Baptiste Queru j...@android.com wrote:Oh, ah, I had... On Sat, Feb 7, 2009 at 11:28 AM, Romain
[android-developers] Re: SlidingDrawer not working with RC33
too bad . shouldn't be a complicated change. well for time being i'll continue to use that http://code.google.com/p/android-misc-widgets/source/browse/trunk/android-misc-widgets/src/org/miscwidgets/widget/Panel.java Any chance to see a kind of home screen container widget where you can drop your views and flip through them ? Right now we're using extended ( so now it' can accept any view(s) with in itself ) code from workspace for that, but it'll be nice to see this sometime in the future as official container. On Feb 8, 1:48 pm, Romain Guy romain...@google.com wrote: That is a good news. May i ask a request, since you guys making a public widget , could you provide little bit flexibility where this widget ca attached to . Won't happen for cupcake. And ability to change drawable of the handle would be nice as well. You already can. The handle is any view you want. -- 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 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
Any chance to see a kind of home screen container widget where you can drop your views and flip through them ? Right now we're using extended ( so now it' can accept any view(s) with in itself ) code from workspace for that, but it'll be nice to see this sometime in the future as official container. I don't see this widget move to the framework in the foreseeable future. The goal of the framework is not to offer any type of widget, but commonly used widgets. On Feb 8, 1:48 pm, Romain Guy romain...@google.com wrote: That is a good news. May i ask a request, since you guys making a public widget , could you provide little bit flexibility where this widget ca attached to . Won't happen for cupcake. And ability to change drawable of the handle would be nice as well. You already can. The handle is any view you want. -- 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 -- 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 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
Can you please report this issue in http://b.android.com/ ? (a plain copy-paste will do). Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that android.internal.widget.SlidingDrawer widget had changed between RC30 and RC33. On RC33 it fails to inflate the layout XML complaining that: The handle attribute is required and must refer to a valid child This is the XML I am trying to inflate: com.android.internal.widget.SlidingDrawer android:id=@+id/drawer android:layout_width=fill_parent android:layout_height=wrap_content android:topOffset=5px android:bottomOffset=7px android:handle=@+id/playlistHeader android:content=@+id/playList ImageView android:id=@id/playlistHeader android:focusable=true android:clickable=true android:scaleType=center android:src=@drawable/ic_mp_current_playlist_btn android:layout_height=56dip android:layout_width=fill_parent / ListView android:id=@+id/playList android:layout_width=fill_parent android:layout_height=fill_parent android:background=@color/grid_dark_background/ /com.android.internal.widget.SlidingDrawer The XML above has both the content and the handle attribute and worked fine in RC30? Does anyone know what has changed and how to fix it? Stefan -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
No, SlidingDrawer is a private widget. It is not supported. On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue in http://b.android.com/ ? (a plain copy-paste will do). Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that android.internal.widget.SlidingDrawer widget had changed between RC30 and RC33. On RC33 it fails to inflate the layout XML complaining that: The handle attribute is required and must refer to a valid child This is the XML I am trying to inflate: com.android.internal.widget.SlidingDrawer android:id=@+id/drawer android:layout_width=fill_parent android:layout_height=wrap_content android:topOffset=5px android:bottomOffset=7px android:handle=@+id/playlistHeader android:content=@+id/playList ImageView android:id=@id/playlistHeader android:focusable=true android:clickable=true android:scaleType=center android:src=@drawable/ic_mp_current_playlist_btn android:layout_height=56dip android:layout_width=fill_parent / ListView android:id=@+id/playList android:layout_width=fill_parent android:layout_height=fill_parent android:background=@color/grid_dark_background/ /com.android.internal.widget.SlidingDrawer The XML above has both the content and the handle attribute and worked fine in RC30? Does anyone know what has changed and how to fix it? Stefan -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. -- 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 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
Oh, ah, I hadn't seen that it was android.INTERNAL.SlidingDrawer (emphasis mine). There's no guarantee of compatibility of private APIs between versions. JBQ On Sat, Feb 7, 2009 at 11:28 AM, Romain Guy romain...@google.com wrote: No, SlidingDrawer is a private widget. It is not supported. On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue in http://b.android.com/ ? (a plain copy-paste will do). Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that android.internal.widget.SlidingDrawer widget had changed between RC30 and RC33. On RC33 it fails to inflate the layout XML complaining that: The handle attribute is required and must refer to a valid child This is the XML I am trying to inflate: com.android.internal.widget.SlidingDrawer android:id=@+id/drawer android:layout_width=fill_parent android:layout_height=wrap_content android:topOffset=5px android:bottomOffset=7px android:handle=@+id/playlistHeader android:content=@+id/playList ImageView android:id=@id/playlistHeader android:focusable=true android:clickable=true android:scaleType=center android:src=@drawable/ic_mp_current_playlist_btn android:layout_height=56dip android:layout_width=fill_parent / ListView android:id=@+id/playList android:layout_width=fill_parent android:layout_height=fill_parent android:background=@color/grid_dark_background/ /com.android.internal.widget.SlidingDrawer The XML above has both the content and the handle attribute and worked fine in RC30? Does anyone know what has changed and how to fix it? Stefan -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. -- 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 -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
Even worse, SlidingDrawer will move to android.widget in Cupcake :)) (And thus become public API.) On Sat, Feb 7, 2009 at 12:14 PM, Jean-Baptiste Queru j...@android.com wrote: Oh, ah, I hadn't seen that it was android.INTERNAL.SlidingDrawer (emphasis mine). There's no guarantee of compatibility of private APIs between versions. JBQ On Sat, Feb 7, 2009 at 11:28 AM, Romain Guy romain...@google.com wrote: No, SlidingDrawer is a private widget. It is not supported. On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue in http://b.android.com/ ? (a plain copy-paste will do). Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that android.internal.widget.SlidingDrawer widget had changed between RC30 and RC33. On RC33 it fails to inflate the layout XML complaining that: The handle attribute is required and must refer to a valid child This is the XML I am trying to inflate: com.android.internal.widget.SlidingDrawer android:id=@+id/drawer android:layout_width=fill_parent android:layout_height=wrap_content android:topOffset=5px android:bottomOffset=7px android:handle=@+id/playlistHeader android:content=@+id/playList ImageView android:id=@id/playlistHeader android:focusable=true android:clickable=true android:scaleType=center android:src=@drawable/ic_mp_current_playlist_btn android:layout_height=56dip android:layout_width=fill_parent / ListView android:id=@+id/playList android:layout_width=fill_parent android:layout_height=fill_parent android:background=@color/grid_dark_background/ /com.android.internal.widget.SlidingDrawer The XML above has both the content and the handle attribute and worked fine in RC30? Does anyone know what has changed and how to fix it? Stefan -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. -- 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 -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. -- 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 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
After digging a bit around in the source code, it looks like the namespace used for the attributes of the internal widgets has changed in RC33 from xmlns:android=http://schemas.android.com/apk/res/ android to some other namespace (probably something like http://schemas.android.com/apk/res/android.intenral ??) and that caused the SlidingDrawer to not find its attributes. Well... one should never rely on internal classes, but... the SlidingDrawer is actually so useful... I am glad it will make it as an officially supported class. On Feb 7, 4:34 pm, Romain Guy romain...@google.com wrote: Even worse, SlidingDrawer will move to android.widget in Cupcake :)) (And thus become public API.) On Sat, Feb 7, 2009 at 12:14 PM, Jean-Baptiste Queru j...@android.com wrote: Oh, ah, I hadn't seen that it was android.INTERNAL.SlidingDrawer (emphasis mine). There's no guarantee of compatibility of private APIs between versions. JBQ On Sat, Feb 7, 2009 at 11:28 AM, Romain Guy romain...@google.com wrote: No, SlidingDrawer is a private widget. It is not supported. On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue inhttp://b.android.com/? (a plain copy-paste will do). Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that android.internal.widget.SlidingDrawer widget had changed between RC30 and RC33. On RC33 it fails to inflate the layout XML complaining that: The handle attribute is required and must refer to a valid child This is the XML I am trying to inflate: com.android.internal.widget.SlidingDrawer android:id=@+id/drawer android:layout_width=fill_parent android:layout_height=wrap_content android:topOffset=5px android:bottomOffset=7px android:handle=@+id/playlistHeader android:content=@+id/playList ImageView android:id=@id/playlistHeader android:focusable=true android:clickable=true android:scaleType=center android:src=@drawable/ic_mp_current_playlist_btn android:layout_height=56dip android:layout_width=fill_parent / ListView android:id=@+id/playList android:layout_width=fill_parent android:layout_height=fill_parent android:background=@color/grid_dark_background/ /com.android.internal.widget.SlidingDrawer The XML above has both the content and the handle attribute and worked fine in RC30? Does anyone know what has changed and how to fix it? Stefan -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. -- 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 -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. -- 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 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
That means your app will break in cupcake though. Please, please don't use private APIs, it only hurts the users :( On Feb 7, 2009 1:43 PM, Stefan skyntc...@gmail.com wrote: After digging a bit around in the source code, it looks like the namespace used for the attributes of the internal widgets has changed in RC33 from xmlns:android=http://schemas.android.com/apk/res/ android to some other namespace (probably something like http://schemas.android.com/apk/res/android.intenral ??) and that caused the SlidingDrawer to not find its attributes. Well... one should never rely on internal classes, but... the SlidingDrawer is actually so useful... I am glad it will make it as an officially supported class. On Feb 7, 4:34 pm, Romain Guy romain...@google.com wrote: Even worse, SlidingDrawer will move ... On Sat, Feb 7, 2009 at 12:14 PM, Jean-Baptiste Queru j...@android.com wrote:Oh, ah, I had... On Sat, Feb 7, 2009 at 11:28 AM, Romain Guy romain...@google.com wrote:No, SlidingDraw... On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue inhttp://b.android.com/? (a plain copy-paste will do).Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that ... romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private... 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 suppo... --~--~-~--~~~---~--~~ You received this message because you are subs... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
Even worse, it hurts the entire ecosystem, by making users believe that plaftorm upgrades have bugs when in fact the applications are broken to start with. JBQ On Sat, Feb 7, 2009 at 3:18 PM, Romain Guy romain...@google.com wrote: That means your app will break in cupcake though. Please, please don't use private APIs, it only hurts the users :( On Feb 7, 2009 1:43 PM, Stefan skyntc...@gmail.com wrote: After digging a bit around in the source code, it looks like the namespace used for the attributes of the internal widgets has changed in RC33 from xmlns:android=http://schemas.android.com/apk/res/ android to some other namespace (probably something like http://schemas.android.com/apk/res/android.intenral ??) and that caused the SlidingDrawer to not find its attributes. Well... one should never rely on internal classes, but... the SlidingDrawer is actually so useful... I am glad it will make it as an officially supported class. On Feb 7, 4:34 pm, Romain Guy romain...@google.com wrote: Even worse, SlidingDrawer will move ... On Sat, Feb 7, 2009 at 12:14 PM, Jean-Baptiste Queru j...@android.com wrote:Oh, ah, I had... On Sat, Feb 7, 2009 at 11:28 AM, Romain Guy romain...@google.com wrote:No, SlidingDraw... On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue inhttp://b.android.com/? (a plain copy-paste will do).Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that ... romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private... 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 suppo... -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
Yes, I do agree that relying on private APIs is dangerous and should be avoided for all the reasons you mention. (The only reason I posted my findings is to save somebody the debugging time as it was not obvious what was the reason at first) This brings another related question. Is there a single place where we as developers can see what has changed between the public releases of the API's for example from RC30 = RC33? - (preferably both internal and external changes)? The only thing I could find is that RC33 has fixed several bugs and added several features, but nothing specific about what has changed and what bugs have been fixed. Stefan On Feb 7, 6:21 pm, Jean-Baptiste Queru j...@android.com wrote: Even worse, it hurts the entire ecosystem, by making users believe that plaftorm upgrades have bugs when in fact the applications are broken to start with. JBQ On Sat, Feb 7, 2009 at 3:18 PM, Romain Guy romain...@google.com wrote: That means your app will break in cupcake though. Please, please don't use private APIs, it only hurts the users :( On Feb 7, 2009 1:43 PM, Stefan skyntc...@gmail.com wrote: After digging a bit around in the source code, it looks like the namespace used for the attributes of the internal widgets has changed in RC33 from xmlns:android=http://schemas.android.com/apk/res/ android to some other namespace (probably something likehttp://schemas.android.com/apk/res/android.intenral ??) and that caused the SlidingDrawer to not find its attributes. Well... one should never rely on internal classes, but... the SlidingDrawer is actually so useful... I am glad it will make it as an officially supported class. On Feb 7, 4:34 pm, Romain Guy romain...@google.com wrote: Even worse, SlidingDrawer will move ... On Sat, Feb 7, 2009 at 12:14 PM, Jean-Baptiste Queru j...@android.com wrote:Oh, ah, I had... On Sat, Feb 7, 2009 at 11:28 AM, Romain Guy romain...@google.com wrote:No, SlidingDraw... On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue inhttp://b.android.com/?(a plain copy-paste will do).Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that ... romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private... 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 suppo... -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: SlidingDrawer not working with RC33
When a new SDK is posted, there is a complete API diff and overview of the changes. However, there is very little change to the platform APIs in 1.1, so there isn't much to say about this one. I'm not sure when an SDK for it will be available. Also, out of curiosity, how did you go about using the private class? If you are actually using the SDK, you shouldn't be able to use any of the private classes, just to protect people from accidentally using things that will break on them. Finally, if there is a class like this in the internal implementation that you really want to use, just copy it out and build the copy in to your own code. That way your code won't break when the system changes. On Sat, Feb 7, 2009 at 4:10 PM, Stefan skyntc...@gmail.com wrote: Yes, I do agree that relying on private APIs is dangerous and should be avoided for all the reasons you mention. (The only reason I posted my findings is to save somebody the debugging time as it was not obvious what was the reason at first) This brings another related question. Is there a single place where we as developers can see what has changed between the public releases of the API's for example from RC30 = RC33? - (preferably both internal and external changes)? The only thing I could find is that RC33 has fixed several bugs and added several features, but nothing specific about what has changed and what bugs have been fixed. Stefan On Feb 7, 6:21 pm, Jean-Baptiste Queru j...@android.com wrote: Even worse, it hurts the entire ecosystem, by making users believe that plaftorm upgrades have bugs when in fact the applications are broken to start with. JBQ On Sat, Feb 7, 2009 at 3:18 PM, Romain Guy romain...@google.com wrote: That means your app will break in cupcake though. Please, please don't use private APIs, it only hurts the users :( On Feb 7, 2009 1:43 PM, Stefan skyntc...@gmail.com wrote: After digging a bit around in the source code, it looks like the namespace used for the attributes of the internal widgets has changed in RC33 from xmlns:android= http://schemas.android.com/apk/res/ android to some other namespace (probably something likehttp:// schemas.android.com/apk/res/android.intenral ??) and that caused the SlidingDrawer to not find its attributes. Well... one should never rely on internal classes, but... the SlidingDrawer is actually so useful... I am glad it will make it as an officially supported class. On Feb 7, 4:34 pm, Romain Guy romain...@google.com wrote: Even worse, SlidingDrawer will move ... On Sat, Feb 7, 2009 at 12:14 PM, Jean-Baptiste Queru j...@android.com wrote:Oh, ah, I had... On Sat, Feb 7, 2009 at 11:28 AM, Romain Guy romain...@google.com wrote:No, SlidingDraw... On Sat, Feb 7, 2009 at 7:18 AM, Jean-Baptiste Queru j...@android.com wrote: Can you please report this issue inhttp://b.android.com/?(ahttp://b.android.com/?%28aplain copy-paste will do).Thanks, JBQ On Sat, Feb 7, 2009 at 6:54 AM, Stefan skyntc...@gmail.com wrote: It appears that ... romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private... 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 suppo... -- Jean-Baptiste M. JBQ Queru Android Engineer, Google. -- Dianne Hackborn Android framework engineer hack...@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. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
