I already did, I just need to fix some other issues before I can release a build.
One thing I have noticed with the offline edition is that after dragging an .ino file to the app, it sometimes comes up with a white screen and freezes. This occurs regularly when you are building / debugging and replacing the running game with a new version of the same .ino,
ino file? Don’t you mean hex? Does the same thing happen with the online version?
I’ll try to replicate this on a Mac at work, as soon as I get a chance.
Yes sorry .HEX file.
To be honest, I have not tried it on the online version.
Ah, ok. A lot of code has changed since the last release builds, so it’s possible the problem isn’t there anymore.
While I’m at it: Is anyone using the IDE/debugger? Would anyone mind if I removed it? An IDE is a lot of work, people have their own and they’re forced to have the Arduino IDE installed because of drivers anyway. It’d be simpler to just implement GDB support.
I don’t use it personally.
I want an easy way to go from the arduino ide straight to the abe emulator, the only solution I could think of is associate .ino with the program and build straight after opening, any other ideas?
Associate the program with hex files. After a build, double-click that. When you make a new build, the emulator should reload automatically.
Can the emulator detect that the associated .HEX file has changed and refresh itself? That would be cool.
Yes, it does that. I haven’t tested it on a Mac, though.
so uh how do I associate the file type, do you do it in-app or…
For now, the regular windows way: Right click the file, Open With, etc.
Edit: At least, I think that’s the way. I’ve been using Linux.
Seriously? I have been dragging the HEX file manually each time as I haven’t noticed it restarting. Is that in a yet to be released version?
All the cool guys are on Macs (and me)
Auto-reload doesn’t work with drag-and-drop, unfortunately. When you drop a file in, the emulator gets the contents of the file instead of a path to it, so it can’t watch the file.
Ah … so I have to ‘Open With’ ?
I think so, but MacOS often likes to think different.
It works, but the sound isnt working.
Some sound libraries need processor features that are still in progress.
Does it work with 1943?
Im using arduboytones.
Are you sure sound is enabled? Each time you run a hex, the emulator starts with a blank EEPROM, which means, by default, sound is off.