Might be time for you to leave the list. Your attitude is not wanted here. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sayed Arian Kooshesh Sent: Tuesday, December 13, 2011 10:51 PM To: Discussions related to Mono for Android Subject: Re: [mono-android] Threading with Rotation
i'm sorry if my responses seem flamy but the majority of the work i've had lately is fixing code of programmers like asshole here who have no idea how to prgramm. How do they get jobs? I just wonder and wonder. Do the clients go on like freelancer.com hoping to get low bid? Don't you know that's how you get FUCKED? I mean, at least hire some talent European (like the people who mange this list) or fucking stop hiring Indians who don't know how to program, write shiity, shitty, code, and end up on lists like this asking stupid ass questions about shit that the developers don't need to help then with. If you can't use c# how it should be, why are you using it to write an android app. You know it's gonna leak memory and fail... fucking shit programmer. I swear to god I might just hire someone to beat the shit out of these guys. That might teach them to not take jobs that they can't handle. On Tue, Dec 13, 2011 at 10:46 PM, Sayed Arian Kooshesh <[email protected]> wrote: > please stop using threads. pleas learn backgroundworker. or i will > find you. I will cut you open. I will eat your innards. is that threat > enough to make you write GOOD code? or are you forever doomed to bitch > on lists like this because you have problems. the problems being > shitty code and the solution being you STOP being a fucking > programmer. > > On Tue, Dec 13, 2011 at 9:31 PM, Jonathan Pryor <[email protected]> wrote: >> On Nov 16, 2011, at 1:10 PM, emalamisura wrote: >>> A common issue with maintaining state is handling Rotation with >>> multiple threads in Android. For instance if you start a thread, >>> and then rotate the phone before the thread is done with its work >>> Android destroys the previous Activity and generates a new one. Any >>> references you had to your previous activity will cause a reference >>> exception. >> >> Right. Don't do that. :-) >> >> I'm also not sure what scenario you're thinking of. Activities are tied to >> their Main thread -- it isn't safe to interact with them except via the main >> thread or Activity.RunOnUiThread() -- and anything associated with the >> Activity follows the same rules as well. This would include the >> LastNonConfigurationInstance value, as used at: >> >> http://stackoverflow.com/a/8331994/83444 >> >> So the primary question is this: why are multiple threads using an Activity >> instance? If it's to use Activity.RunOnUiThread(), use an alternative, such >> as a Handler instance over the MainLooper: >> >> >> http://support.xamarin.com/customer/portal/questions/34836-toast-in-s >> ervice >> >>> This becomes even more difficult >>> to handle in MonoDroid because alot of the semantics used in Java >>> such as using an internal static class inside your activity can't >>> easily be reproduced in C# >> >> I also don't understand this. Java's `static` nested classes are ~identical >> to C# nested types; it's non-`static` nested classes which differ. >> >> Thanks, >> - Jon >> >> _______________________________________________ >> Monodroid mailing list >> [email protected] >> >> UNSUBSCRIBE INFORMATION: >> http://lists.ximian.com/mailman/listinfo/monodroid > > > > -- > Extreme Knowledge is not something for which he programs a computer > but for which his computer is programming him. > > -Wozniak -- Extreme Knowledge is not something for which he programs a computer but for which his computer is programming him. -Wozniak _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
