Re: [mono-android] Xamarin Android Release Build Error

2014-04-09 Thread Agustin Gimenez
Ok, thanks for the update. 2014-04-09 11:02 GMT+02:00 venkatesh : > Hi, > > Kindly suggest on this issue as we are struggling this issue past two days > for release build. > > > Thanks > > Venkatesh.R > > > > -- > View this message in context: > http://mono-for-android.1047100.n5.nabble.com/Xam

Re: [mono-android] Android devices with Barcode-scanner Hardware

2014-03-11 Thread Agustin Gimenez
Hi Earan. This is a supposition, so may be completely wrong ;). Did you tryed to enumerate the COM ports from the device and read from them when you scan something? The most usual on devices with integrated hardware is to connect it through virtual COM ports, also, in the datasheet should be som

Re: [mono-android] Is monotouch right for me?

2012-09-24 Thread Agustin Gimenez
Hi. For a tetris-like game, using monogame with monotouch/droid as miljenko said and XNA, you will reuse nearly all the code between all three platforms. But for drawing is another history, drawing in real time to a texture is not the straightest operation to do in XNA or OpenGL, I find easier to

Re: [mono-android] Is monotouch right for me?

2012-09-23 Thread Agustin Gimenez
Hi. First of all, I must say programming a game is not as simple as it seems. If you don't have any knowledge about OpenGL and XNA it's going to be hard beside the tools you use. Ok, so, first of all you must create an engine with an abstraction layer to reuse the máximum possible code. If you

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Agustin Gimenez
LOL... ¿seriously? ¿someone with that name can be so moron to say that? ROFL Also, let other people live what they like, seeing the code it's obvious for everyone that is not the code from a pro, but hey, every of us had to learn in some point of time, no? Instead opf saying nonsenses apport

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Agustin Gimenez
Sayed, when the DownloadString function (the main function for the thread) is finished, it's destroyed and the webclient is de-referenced, the only reference left is the one on the async call which is eliminated when the async call finishes, so, your im-so-good theroy is wrong WORNGGG!!! XD WevCli

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Agustin Gimenez
I agree that the threadpool calls are superfluous, calling directly to the async methods would be the correct thing, but that had to not influence on memory leakage inside a webclient. As i said WebClient inherently leaks meory (at least in the fw 2.0, since then I only used HttWebRequests because

Re: [mono-android] Simple project with massive memory leak

2011-11-26 Thread Agustin Gimenez
Are YOU so moron that you don't see what that program does?? Creates a thread, the thread starts an async call, when the call is finished a new thread is created and the process starts again. A workerthread is automatically disposed when its main function is finished, so there is going to be only