The emulator is so slow as to be almost totally pointless on my computer, which seems to be a very common experience... takes ages to load, and then once it finally does it goes at maybe a fiftieth of the speed of my phone, hence it gives me very little idea what the thing's going to be like in practice.
And yet it's the default action when I press the 'play' button or Ctrl+r - which is of course what I've been conditioned to do when I want to test out my sketches, by years of using Processing. Not only that, but once I absent-mindedly press that button - which I still do even after a few weeks of doing Android - pressing 'Stop' doesn't interrupt the process; there seems to be no way to halt the juggernaut, I just need to wait and wait for this useless emulator window to appear and then close it when it does.
Sorry, I realise this is a moany post, I've got a headache. Is there any chance we could have an option to just disable the emulator, at least while my phone is attached? Or a Stop button that stops it loading after I accidentally tell it to? I would be deeply grateful.
Somewhat relatedly, are there plans to make it so that standard-mode Processing doesn't choke on things like orientation(LANDSCAPE) so that we can switch between modes a bit more easily (rather than having to comment out such things every time)?
Heh, orientation isn't the only problem switching between the modes, it gets really annoying when you use SoundPool or anything that's Android only. You're pretty much stuck in one mode from that point on. I've completely abandoned the Processing IDE after my first app, moved to Ubuntu and am currently happily using Eclipse, although it doesn't cure the emulator problem. The best solution is to get a real device. I just click Run and it's running on my tablet in 5-10 seconds.
My trouble is that I have a real device, but I haven't got the hang of never running on the emulator by mistake. I can't imagine even trying seriously to develop using the emulator rather than a real phone or whatever, but I suppose it's okay if you have a computer at least ten times as powerful as mine...
I too am having trouble with the default action of 'Run' when in Android mode. I realize it's a matter of being more conscious when running my sketch than in my typical Processing usage but no matter what, after a couple hours in the IDE I inevitably hit the play button and have to wait for the emulator to load up before I can shut it off, which also happens to mess up Processing's connection to my physical device (which is not fixed by the "Reset Connections" option make this kind of a useless menu item) and then I have to shut down and restart the IDE. Pretty annoying, I must say. Wouldn't this be solved by making 'Run on Device' the default action and 'Run in Emulator' the secondary (more conscious) choice?
How do I "vote up" or request this feature change?