Android news tutorial Videos

+Sukumar H thanks, it feels awesome to fix your own stuff doesnt it, reminds me of today morning when i fixed a bug :D

Found the answer. By setting the height of the recyclerview, it becomes scrollable. Placing the recyclerview inside the scrollview gives an error.

+slidenerd All the Best..I am hoping to add a lot more to my knowledge set..Thanks and do keep up the excellent work..

+Dhaval Chheda first of all, wish you a very happy new year and may you take the initiative to turn this year into a prosperous one :) second of all, i am adding a new android course coming up here in 10 days https://goo.gl/JqAUyg stay tuned, I ll post an update about it here https://goo.gl/ASF501

+slidenerd Alright, sorry. I didn't mean to sound condescending. The problem I'm referring to is basically this: If say, for example, you start an Async Task from an Activity, you would need a reference to that Activity from within the Async Task to call it back with results when the task is done. Now, the obvious solution would be to just pass the Activity along to the Async Task which in turn holds a reference to it until the task is done. That works fine as long as the Activity is alive. However, if a configuration change occurs, for example because the device is rotated, the entire Activity is destroyed and recreated by the system. Now, if that recreation process takes place while the AsyncTask is running and holds a reference to the Activity, it cannot be destroyed and stays alive basically forever, yet another Activity is created anyway. Thus, you end up with two activities one of which is never used again, but also isn't garbage collected because the async task refers to it. Now, a common way to solve this issue is to wrap the Activity inside a WeakReference object which basically tells the garbage collector that the object can be destroyed at any time, so you can avoid a memory leak that way.This is what I'm talking about: //stackoverflow.com/questions/18297378/weakreference-asynctask-pattern-in-androidNow, in a similar way, I was wondering if the Fragment might leak if you pass it as a ClickListener to the Adapter which then strongly holds a reference to it. If said Fragment is destroyed and recreated, the old Fragment object might not be garbage collected because the Adapter is still refering to it. So I was asking whether this is an issue here. But I don't think it is because you're recreating the adapter and resetting the clicklistener in the onCreateView method, so I guess this whole wall of text was all for nothing. :D Oh, well, happy new year and keep up your good work! :)

+Christian Meyer whoa whoa big guy, I didn't understand that :) care to elaborate a bit? happy new year for starters

+Asad Khan why used v.getPosition()?

+slidenerd yea I solved this problem. but there's another thing.. I want to open multiple activities from this drawer. Like separate activity for each element of navigation drawer. How can I do that? Plz reply A.S.A.

+Asad Khan getAdapterPosition is the way to go I believe

+Asad Khan //lmgtfy.com/?q=cannot+resolve+method+getPosition+recyclerview+android

+Asad Khan got it Lol :P i was using dot instead of comma. Silly..

+Abishek AB what do you mean?

+സനൽ sure, thanks, can you please rate my videos 5 star here if you didnt do so //udemy.com/u/vivekramesh2 thanks in advance :)

Thank you so much you came so clutch just now

thanks bro this was so useful !