Androidx23



matt gaunt: another androidoffice hours from the somewhat snowy london. my name is matt gaunti'm joined with-- chris banes: chris banes. matt gaunt: yep.


Androidx23, and we're going to be discussingall things android. here's your disclaimer, wedon't talk about future releases, or futureannouncements, or anything that we might be doing.


we are literally here to talkabout the apis that we've got and to try and helpyou guys out. chris banes: sorry we'rea bit late today. we ran into a couple oftechnical difficulties. matt gaunt: one afterthe other. chris banes: yep. matt gaunt: but we're here. it's all good. chris banes:we gotrich cc giuseppe


as well in the hangout. hey, [? giuseppe, ?] how are you doing? giuseppe: thanks, good. wiebe elsinga:hi guys. male speaker: i just joined incase i could help with the technical difficulties. but i'm actually in mountainview at the moment. so it's six o'clockin the morning.


so i'm going to drop out andleave these guys to it. i was useless anyways. i'll catch you guys later. cheers everyone. wiebe elsinga: bewareof the jet lag. chris banes: how'sthings for you? wiebe? wiebe elsinga:who me? chris banes: yeah, wiebe.


wiebe elsinga: great,a little bit tired. but it's the flu season soeverybody's a little bit sick. chris banes: yeah, not good. matt gaunt: yeah, i just aboutmanaged to stave away from that from ces. chris banes: anythinginteresting at ces when you went? matt gaunt: yes, lots of newgoogle tv devices were in there, which i'm sure peoplewere keen to see.


chris banes: [laughter] matt gaunt: we announcedpartnerships with asus, netgear, tco. lg announced a new set oftvs, as did hisense. so it was amazing. no hand involved. hisense had massive billboardsand has snap films up everywhere. it's a really good event,really, really


fun place to start. lots of miracast devicesas well. start to lay outthe wood work. chris banes: that's good. cool. any questions in the room? giuseppe: [speakingforeign language. chris banes: say thatagain, giuseppe. matt gaunt: everyone's havingtechnical issues as well.


chris banes: wiebe, i know youhave a question, because it was in the moderator. do you want to ask it live? wiebe elsinga: yeah. now what we see, we seemore televisions. we see android'ssmart watches. we see google glasses. so i was wondering if there's agood technique to do pair to pair with different devices.


chris banes: wi-fi direct isthe way we would prescribe doing it from now on, really. network discovery, idon't really know what the acronym is. matt gaunt: nds, was it? chris banes: nds. there is a big training sampleon developer.android.com which is actually really good. that's the way i'd point you to,mainly because it's going


to be bundled throughandroid from now on. and you have quicker p2paccess [inaudible]. so that's the way [inaudible]. matt gaunt: i think for me-- i don't think we've got to thepoint where we've got a unified api, onesize fits all. i think, obviously, googletv we have any mode. but that's very much the case ifyou fling it off to the tv, you can discover it.


but you can't then startgoing backwards. then when you start talkingabout smartwatches, obviously all of them are using bluetoothas their way communication that have wi-fi. so i don't think there is justa one solution fix all. obviously if there is a servicethat you can use that does all of this for you,then look into it. but obviously you'd start buyinginto something that they suddenly decide stopsupporting it, or they change


it, or suddenly there is a newdevices they don't want to support, you are kind oftied in to that point. so i think nds stuffis probably quite a safe way to go. just try and do whatever youthink is best and it fits in right with your solution. just try to bear in mind, in thefuture down the line, that you may need to swap it out. wiebe elsinga: i will followthe tutorial online, then.


chris banes: yeah it'sa nice tutorial, nice code and that stuff. wiebe elsinga:cool, thank you. matt gaunt: cheers, wiebe. chris banes: hey, it's lookslike we've got more guys. we've got yossi. yossi elkrief: hi, guys. chris banes: hey,how do you do? yossi elkrief: i'm fine.


i have a little questionif i can ask. or is there someoneelse on the line? chris banes:there is,but go for it. ask the question. yossi elkrief: ok. i'm trying to see-- to do some poc aboutvideoview. and what i was trying to do isbasically have a full screen videoview inside a view pager.


and on the video view i want toshow some custom buttons. but every time i try to load thevideo to the videoview, i get an error that the videoview cannot play the file, even though when commenting allthe buttons or all of the draw bars on top ofthe video view, the file plays correctly. any known issue about this,or something like that? matt gaunt: that's very weird. you're definitely just usinga plain old video viewer.


you're not using the youtubeplayer api are you? yossi elkrief: no, no, videoview from the android. matt gaunt: that shouldn'tcause an issue. chris banes: have you tried withthe buttons, but not in a view pager? yossi elkrief: yeah, alsothe same results. chris banes: it worked? yossi elkrief: no,it doesn't work. wiebe elsinga: where is yourvideo source coming from?


yossi elkrief: fromthe sd card that i have it on an sd card. i also tried to do iton raw data files. wiebe elsinga: and thepermissions is set correctly? yossi elkrief: sorry,didn't hear you. wiebe elsinga: the permissionis set correctly? yossi elkrief: yes,yes of course. i can-- if i just do a simple viewwith videoview on it, and


attach the media file, andi just click on it. and it plays correctly. and the only problem is when i'mstarting to add the image buttons, or any other textviews, or overlays on it inside the relative layout, orlinear layout, whatever you want, and the view doesn'tplay the video. chris banes: video view isbasically a glorified surfaceview with lock integratedmedia player from [? chassis. ?]


and surfaceview drawsdifferently to other views. it sort of punches rightfor the window. so android doesn't solveoptimization stuff to get it to [inaudible]. and have a look at thesurfaceview documentation, because i remember there beingflag on there where you can set a compatibility mode to makeit draw things on top. but i can't remember offthe top of my head. it's been a while sincei've used it.


but have a look at surfaceviewand that class of documentation, becausei'm pretty sure there's a flag on there. yossi elkrief: ok i'lltry to see it. and another question, ididn't encounter it. but we have a view pager witha surfaceview on it. and basically when you do thescrolling, scroll from side to side, you see a black surface. and the view doesn't renderfrom one view


page switch to another. you know, like on the camerawhen you switch from live video to the gallery? you see the gallery hasa black overlay? chris banes: the reason forthat is because the way surfaceview works in that itpunches for all the windows. so imagine your surface view isright at the back of your views, and it sort ofpunches through. so what your actually seeing itthe very back window, the


black, that's whatthe black is. and it's just becausethe way it draws is different to other views. there's no real way around it,unfortunately, other than not using the surfaceview. obviously don't use it if youdon't really have to. yossi elkrief: yeah, i didn'tsee it until now. we tried to do something withthe camera preview, and just do a view pager scrollingleft to right.


and we saw that basicallythe view doesn't completely render. because on the galaxy nexus withthe jelly bean, it works flawlessly. you don't see theblack rendering. on different devices, like onthe samsung s2 or s3, you see the black window stays untilthe full window has been switched in. chris banes: this is probablyfixed in jelly bean then.


but it's just theway surfaceview works, from what i know. thanks guys, i'll try. male speaker 2: hi, cani ask a question? matt gaunt: yeah, go for it. male speaker 2: i havetwo questions please. the first one is how to changethe stack overflow icon programmatically. like when switching when i haveaction bar overflow, it


switches programmatically. any idea? chris banes: you wantto switch the icon? male speaker 2: theicon, yeah. the scenario is thati have several-- i have a split action bar, theaction bar, and then the action mode as well, which isthe contextual action bar, another term for it. and i have two differentbackgrounds for the action bar


and the split action bar. they are both in contrastto one another. so the overflow looks hiddenon the dark if it's light and light. and it looks hiddenin vice versa. chris banes: [inaudible] is to use the [inaudible] and not use the [inaudible] action bar.


just use action [inaudible]. we access [inaudible] there's no way. if you get access to the sourcefrom the drawables, then you can change it. male speaker 2:ok. thank you. and then my second questionis, i want to play-- alexander, hi.


can you please turn offthe microphone? i think we have backgroundnoises. the microphone, notthe earphones. chris banes: it's all right,it'll be just me anyways. don't worry. male speaker 2: so mysecond question is regarding hls mime type. i understand that android asof 3.0 supports hls plane. and i have problems with itbefore they got fixed.


but there isn't any hls mimetype that triggers the activity of the player. i gave the wrong mime type toplay the hls just for default player activity to pop up. but what's the mime type? what's the formal mime typethat the default player supports for hls? matt gaunt: i think hls,you want to package it up as mp4, i think.


and there is something in thatfile which will then-- where is that coming from? male speaker 2: so that'swhat i did. i ran-- i got the mp4 mime type. and it runs, but theremay be players that supports mp4 but not hls. so-- matt gaunt: well, it will be theandroid page platform that


will be supporting hls. the way you want to do it, ifyou wanted to ensure the players that didn't support hlsweren't getting played in that way, using that file,then you'd want to be basically [inaudible]. male speaker 2: sorry,i didn't get it. matt gaunt: you want to be usingthe android version code if you only want it toplay the hls stream on android and above.


male speaker 2: so how do irun only the activity of-- i need to run, specifically, thebuilt-in players activity. right? i invoke intent torun the activity. i'm not using the playeras part of the app. matt gaunt: yeah. yeah so all you want to doinvoke the activity. you want to invoke the activitydepending on which version of androidyou're running.


is that right? male speaker 2: but-- matt gaunt: or hls? male speaker 2: yeah, but-- for example, a samsung isperhaps samsung implement their own activity, andit's a different package name or something. matt gaunt: so what you want tobe doing is basically using the action underscore[inaudible]


intent, and run that way. here's an mp4 filethat [inaudible] is capable of playing it, orthen be given the chance to male speaker 2: ok, so thereis a delay here, sorry. i'm listening. matt gaunt: the other thing iwas going to is, since all versions of android[inaudible] play your hls stream correctly,you basically just want to make sure that youlaunch that intent on those


versions of android and above. male speaker 2: ok. but the problem is that if i runthe intent with mp4 mime type, what will happened is thatplayers that support mp4 will catch this. but i saw some players thatsupport mp4, but do not support hls, which iskind of a wrapper around mp4, that's right. but they still don'tsupport it.


matt gaunt: could you post inthe chat which devices you're referring to? and maybe we can helpdig around. male speaker 2: it's more likewhat players are supported. because if a user installs twoplayers that support mp4 but from the play store, theyinstall two players that support mp4 but not hls, theywon't play my video. matt gaunt:i guess it depends,because if they're using a player which is implementingtheir own media codex and


their own encoding/decoding, andthey're not be relying on the android systems. at which point, i guess, adifficult way would be trying to get that across to a user. i mean, the obvious choice isto, since you know you're going to be able to run it oncertain devices of android, run it in video viewer. that way you kind ofget control of it. there's media controllers youdon't have to do any controls


or handling password, rewinding,et cetera. so it should be relativelytrivial just to add in your own video viewer, whichmight be a good way to get around this. male speaker 2: so how do i skiparound implementing all of the controllers, the fastforward, the seek to bar, and stuff like that? matt gaunt: when you create avideo viewer you can just also set a media controller.


and then provided you set thatmedia controller, which, again, is just a class that isjust handed to you, it'll just [inaudible] the videoviewfor you. so can we request toadd the hls mime type in future releases? matt gaunt: that goes on to amuch larger issue of the way hls handles is itself. so it's not necessarilymime type. i think that would be more to dowith a standard issue of an


android just sitting theresaying here's a mime type, use it for android only. i think it would need to be aslightly bigger discussion. i don't think that's somethingwe could necessarily do. because like i said, i thinkit's one of those things that apple has obviously createdthe standard-- made it so that mp4 is theway of dealing with it. that's kind of the standard. maybe it will change.


so it's kind of more ofjust the activity of the media player. it's just the activity, theintents that the activity of the media player can handle? that's it, right? matt gaunt: yeah, exactly. ok, thanks. chris banes: anyone elsehave a question? male speaker 3: cani ask a question?


chris banes: yeah, sure. male speaker 3: thank you. so i have an app that's[inaudible] that relies on [inaudible] api. and i choose a random songselected by genre. and then i play and theuser has to get us the name and the artist. but i provide the registrationfor these to have the


rankings and so on. but do i have to provide aprivacy policy inside the output, or on the googleplay store in the appropriate section? matt gaunt: so i think theplay store changed its regulations regarding theprivacy policies. you have one now, or-- chris banes: you either have tohave one, or you explicitly say you're not goingto provide one.


matt gaunt: ok. my recommendation would bedefinitely to have one on the play store. and then if you've got aconvenient place where can have in the app and it makessense for you to have it in the app, in terms of you've gota settings page, you can just put it into there. and you've got a nice easy wayof keeping the two in sync, i'd go with that.


i don't see any reason if you'vealready gone through the time to prepare it, andyou've got a spot where it can live in the app without being inthe way, then i'd say just include it. but i don't thinkit's required. male speaker 3: ok but it's nota legal problem if i don't put it in there, putit inside the app? matt gaunt: it's not a legalproblem in terms of us. it's more of a legalproblem, i guess,


between you and the user. i can't really comment becausei don't know that much about it, because i'm not in legal. male speaker 3: no, it isbecause i don't know if i must provide a privacy policy. because the user,to me, is data. so i must protect this data. i have to say ok, this datai've stored is protected. you are right.


chris banes: i would alwaysbundle the privacy policy with the app, just in caseyour app isn't distributed with play store. so if it goes into amazon appstore or any other sort of distribution channel, and theydon't allow you to show a privacy policy, it's alwaysgoing to be with your app. male speaker 3: ok. chris banes: so it'sa fail safe. so i would always do it.


if you took the time to createone, shoving it in your assets folder and then createa web view. it's not much work. male speaker 3: ok, thank you. matt gaunt: i guess it kind ofleads on to a slightly wider picture of [inaudible]. then if the user goes throughthe time to actually hunt that out, then it probably meansthat they're slightly concerned about your app.


and it's probably good way ofputting their mind at ease. that's another way of lookingat it as well? chris banes: so havewe got any more questions in the moderator? go ahead, giuseppe. i knew you'd have one. giuseppe: all right. i have a question aboutthe google drive sdk. is this the right place toask for this question?


chris banes: we can try andanswer, we don't know-- matt gaunt: it's one where youneed rich and nick here. they can go around duringdeveloper days on this. but go for it. giuseppe: ok, that's good. i'm trying to get the token[inaudible] orientation using the new google play services. and i combined this withthe google drive sdk. sometimes the google drive sdk,they turn to me, and now


object, no exception on theupload of the file. but this happened very,very randomly. so this is not a pack, but itstarts something concerning the web server, ori don't know, the services from driver. anyone got some experienceabout that? chris banes: i'd probably guessthat it's the connection issue, maybe? maybe the connection dropped outfor a millisecond while it


was uploading. and it doesn't do any retryingso you might need to do-- implement that yourself. giuseppe: no, i don't know. i already tried to clear thecache and everything. i also found on stack overflowa question like this without any answers. if you want i can sharethe questions. because i believe thatthere is some


problem with the service. chris banes: yeah, share thequestion for the stack overflow link. and we'll try and to give itto rich and nick, because they've got far more experiencefor the drive sdk than we have. giuseppe: ok. i will find it right now andi will put in the chat. so you can go to anotherquestion with someone else.


chris banes: thanks, giuseppe. are there any other questionsin the chat? oh, we're going to getsome moderator. let's get some moderatorquestions on the go. right. so here's a question from jaydixon, who asked, as there's a cache management in the googleplay in that purchase sort of flow in version for it, it'sasking how do you actually clear the cache when you'reactually making changes to


prices, to items, to whateveryou need to, really? do you want to answer? matt gaunt: no, you go for it. chris banes: ok. so from what i gather, whenyou're making changes to your in-app purchases, the googleplay client will actually be notified, and it allinvalidates cache. and so i'm pretty sure you canjust assume that any call that you make, the cache is valid.


i think that's a prettysafe assumption. matt gaunt: i guess the onlytime you might see issues is it does take a long while forupdates in the play store when it comes to billingto actually go through to the app. so you might have towait a little while for that to go through. if you've got a moresolid example, drop us another question.


but yeah, i think, likeyou said, google play will sort it out. chris banes: andrew kelly hasasked, "can you please confirm the current refund period onthe google play store? is there any wayto [inaudible] misses?" matt gaunt: i'd likeanswer to this. no you can not do it. and the main reason i kind oflike that is [inaudible]


if you're trying to find thatout, i question what you're trying to do with it. i like the idea. well, i don't like the idea. i just can easily see howpeople would take advantage of that. chris banes: it's onychanged once. so i can't gather it's not goingto change for a while, if it does.


but we don't know. yeah, [inaudible]. matt gaunt: if the google playteam decides they want to change it, then it is probablydue to customer. they've obviously got a goodreason for doing it. obviously that's whenwe'll make a public statement, et cetera. chris banes: but it's notgoing to be a regular occurrence.


it's not going to be somethingthat happens dynamically. matt gaunt: i think that'spoint where changing it regularly will confusedevelopers as well as consumers, which wedon't want to do. chris banes: we've gotmore questions on the monitor, actually. "how difficult is it to enableprinting from within android? how different are the apis, theversion two and version four?" from kevin.


matt gaunt: i have noexperience with the google print api. so i couldn't comment. have you played with it? chris banes: i haven'tplayed with it. matt gaunt: i don't know,to be brutally honest. that might be a questionto try again next week. we can probably copy it overfrom the moderator. perhaps rich or nick willhave a better idea.


if not, we'll go away andlook at it and come back with an answer. chris banes: yeah all afterthis, because these have come in recently. matt gaunt: i might have achance to look at them. have you got anymore questions? so there's a question, "cananyone tell me how to override slash hide outgoingcalling screen in android?" nejandra, i think.


i could have just destroyedthat name. i'm sorry if i have. so yeah, chris is kinda pointingout that it's the action new outgoing callsbroadcast which you can essentially registerto be overridden. i also recommend lookingat sipdroid. it's an open sourcevoiceover ip app. but generally, i'd say look atthe documentation, you'll get a good idea of what'sgoing on.


and then if you look at anyexamples, then sipdroid is a quite nice way of then goingand digging around. chris banes: i'd worryabout what you're trying to do with this. if you're trying to implementcalling yourself, like if your trying create [inaudible] [? clones ?] or something, thenyes, a valide use case. but if you're trying to sortof hide someone's trying to call their gsm, or whatever, i'dworry about that, because


i'm not sure why you'dneed to do that. matt gaunt: yeah, i thinkit's just a bit of a niche use case. i think the time i had to lookat it was a company that wanted to tell whether you weremaking an international call or not. i'd say be very careful. because like you say, you'rekind of just kind of integrating really heavilywith the core purpose of


someone's phone. chris banes: especially aspeople know what the layout is, how to sort of turn thespeaker on and off, mute, all that kind of stuff. matt gaunt: i think it's theprime candidate for just giving a tutorial. it's like what's going to happenwhen they've installed your app and enabledcertain things. chris banes: i agree.


matt gaunt: so did youwant to look at some? chris banes: yeah. matt gaunt: if anyone hasquestions live, feel free to jump in. chris banes: so andrew kelly,another question from andy. "with the drawable note dpibucket, could you give an explanation of why you wouldwant to use this? and how would the image look onan xhdpi device compared to a mdpi device?


why would i want thisto happen?" matt gaunt: we just had a briefdiscussion about this before we came online. basically if you think of mdpior dpi, et cetera, as being a bucket, it's a range of pixeldensity displays. and it kind of simplifies theway the developers can think about the ui in terms of justroughly, if it's mdpi, then it will use [inaudible]. that's what i have to worryabout, as apposed to each


individual one. but it will still get somelevel of scaling. now say you probably don'thave that much use case wanting to use no dpi. chris gave the example of whereyou wanted to handle the scaling yourself,which is valid. i've used it in the past wherei've wanted to literally just have a pixel perfect image forone single device that was not going to be distributedanywhere.


i'd argue if you were using it,then you're probably using in such a niche use case thatyou're completely aware of what the limitationsare going to be. but yeah, generally i'dsay most people wouldn't need to do this. only if you need to get it outunscaled or untouched, pixel for pixel, exactly the same. i had a long answerto that one. chris banes: primary exampleof when to use it is in


documentation for widgetpreviews, as in version 3 onwards, you've gottenat sort of the end. widgets and listview,gridview, all and the documentation says toput your widget preview in the dpi, just because the launcherdoes all the scaling for you. as an example, it's just gettingrid of user if you want to scan yourself. peter brookes has asked, "arethere any suggestions for respondents of apps affectingyour app, but not free, not


audio channels, given the[inaudible]?" not really. there's no way you can reallycontrol audio manager, how that sort of just distributeschannels. so there is no way, really. matt gaunt: yeah, i thinkgenerally it's the case of kind of the honor system. if you're playing around withthat kind of stuff, i know when you're told to kind ofshow yourself how do it. i can't think of any situationhow you could overcome that,


beyond informing the user aboutwhat's going on and telling them we're trying to dothis but we can't, because of other applications. perhaps consider closing them. chris banes: it would beinteresting what scenarios you've got for this,or why apps are using so many channels. it's got to be interesting howthey're trying to use so many channels to sort of useup your allowance.


chris banes: so if you can givethat in there, put that in the response. matt gaunt: "i'm having apersistent but sporadic problem with my web view. it's consistent acrossdifferent handsets. and i have no clue on what todo." stack overflow, from minnie bell. i like that name. so on 4.0.1, the web viewshows a blank page,


apparently. matt gaunt: so it looks likethey're just trying to display some data just as a string,uploading from a web service, and doing a sort of encoding. can't say i can give youan answer to that one. chris banes: we'll dothat one offline, so there's not one candidate. matt gaunt: so it doesanyone else have any questions in the hang out?


come on, someonemust have one. oh, yeah, we haven'tlooked at hangout. chris banes: yeah, we haven'tlooked at google+. wiebe elsinga: there's not muchquestions, either, there. chris banes: no. so we're not verypopular today. yossi elkrief: back tomy question about the videoview again? chris banes: what'sthat yossi?


yossi elkrief: canyou hear me now? chris banes: yeah, ican hear you now. yossi elkrief: ok, sorry. about the videoview again. basically what i did again, andi just stripped all of the image buttons and the drawablesand stuff from the video view. and put it on the view pagerand it's working. on the view pager.


chris banes: [inaudible]. yossi elkrief: sorry? chris banes: no buttonsand it's working? yossi elkrief: no, no buttonsand it's working. it's loading the video. i can click on it and play,click again, and it pauses and resumes, and so on. any suggestions where to digup, or to see why when i'm adding an image overlayor something on top


of the video is-- chris banes: there'sa flag on surface view from what i remember. i'll have a quick dig now,see if i can find it. matt gaunt: i've seen peopleoverlay their own buttons on video viewer. yossi elkrief: i just postedon the chat a simple app i just stumbled upon. it's called videosuper pop-up, or


something like that. i'm not sure. and basically what it does, ithas some nice neat ui packing to enable a pop-up of all thevideo you will be playing, basically as a drag window. all over your home screen is awidget resize-able, and inside the other applications. and basically you have a windowwith the video playing. and you can interact with theentire screen with different


activities. i think it's using somethingthat it shouldn't use, but i'm not sure. matt gaunt: i've seen examplesof it done a very simplistic apps. i think my biggest concern isthe fact that because it's in a view pager as well, whetherwe're getting to a point where something's just notquite sitting. chris banes: yossi, did you sayit's not working out of a


so if you don't use a viewpager, it doesn't work either? matt gaunt: you've gotthe same problem. yossi elkrief: no,the same problem. i can't play video file. basically when i have thevideoview inside of view pager, it works. outside of view pager,it works. if i add buttons on top ofit, it doesn't work. chris banes: did you say it'snot happening across--


is it happening across allversions of android? yossi elkrief: no. i'm just testing on my nexus7 on my galaxy nexus. i didn't test on the android2.3 or gingerbread. chris banes: there is a methodon surface view called "set z order on top," which will makeyour surfaceview try and draw like a normal view. so if you can try and get accessto the surfaceview from videoview and then call thatmethod, set it to true, it


might work. yossi elkrief: peter brookesposted on the chat, "we overlay buttons on video a loton our app." which app? me code sample. surfaceview sets theorder on top-- oh, it's a game, "broken sword.""set the order on top." chris banes: yeah, can'tremember if you can get the surfaceview from videoview.


yossi elkrief: no, i think ineed to override videoview, or extend videoview, and thentry to get some. chris banes: extendsurfaceview. so yeah, you can justcall "set z order on top" on the videoview. it should work. but it will call, i don'tknow if it will work. [laughter] yossi elkrief: basically itsays the order is just to


change the stacking of theelements on the layers. i can't remember the exactway surfaceview works. but without it, it sort ofpunches view from the back in view window. whereas if you call true on "setz order on top," it does some special stuff where itkind of proxies the view. so it looks like it'sa normal view. i cant remember theexact details. i've done this kind of thingbefore, and doing that worked.


but i don't know aboutyour scenario. chris banes: it would be quiteinteresting if you can load up a small sample that is doingexactly the same thing. it would be interestingto see. i'll try to dig out only thespecific sample for the view pager and stuff. chris banes: thatwould be good. yossi elkrief: and maybe dosome github or something. i'm not sure it will workbecause basically i've tried


to do it in the last couple ofhours, and that's the first time i saw somethinglike that. i did video views before andnever had the problem of doing an image overlay on top of it. yeah, i can't say i'mfamiliar with it. matt gaunt: we've been joinedby someone else. chris banes: that's, ithink, from earlier. any other questions? yossi elkrief: maybe peter.


chris banes: we answeredone of peter's. matt gaunt: yeah, we answeredone of p. brooke's. if not-- chris banes: do we haveany on google+? that one there. matt gaunt: google+ was empty. i think we've gone through. male speaker 2: i'd like toask another question. chris banes: yeah go for it.


male speaker 2: ifthere's time. male speaker 2: so how do i knowif an action is found on the split action bar insteadof the original action bar? chris banes: you don't. male speaker 2: with actionbar [inaudible] perhaps? chris banes: i don't know. i'm sure you could somehow. it's supposed to be transparent,so you're not


supposed to know. you're supposed to set up theapp and then the split action bar will show on certaindevices, mainly phones or small devices. male speaker 2: what if i usedifferent backgrounds for one light and the other one dark? chris banes: so what was that? you can use a light backgroundon the split? male speaker 2: yeah, and darkbackground on the original.


and then i need to switch iconsto show the contrast. chris banes: oh, iunderstand now. don't think any ofthe others do. matt gaunt: i think youjust want to give them different ids. male speaker 2: i don't thinki control the ids. i don't know what the ids are. i don't think there's anyway you can do it. there's no way of findingout [inaudible].


male speaker 2: i didn'thear that while i tried to record it. matt gaunt: cool, welli guess we don't have any other questions. chris banes: lookslike we don't. matt gaunt: anyone else? last chance. going once-- yossi elkrief: going twice,sold to the guy


in the yellow shirt. chris banes: ok, guys. matt gaunt: thankyou very much. yossi elkrief: thanks, guys.


Androidx23

thanks. chris banes: call next week. yossi elkrief: bye. cheers, guys.


Androidx23 Rating: 4.5 Diposkan Oleh: PaduWaras