A workaround for the people trying to enter manual objects in iObserve 1.4.0 and 1.4.1: until the fix is available, enter the name of your object in the first tab, and then the coordinates in the third. You object will be imported.
While developing this new website, I was wondering from where my visitors were coming. The squarespace site make it easy to grab this information. And clearly, people find it directly.
This corresponds basically to what I think since the beginning: iObserve gets its reputation (and downloads) mostly through word-of-mouth. That’s great because I have not enough time and energy to spend for promotion. I did it once however in the famous ‘astrobetter.com‘ website: here, with a follow-up here.
By reading again the comments, I am horrified by the amount of things I promised I’ll develop inside iObserve. These are usually still in the to-do list, but overwhelmed by the new stuff. Achieving a complete release of a software is an exercise of trying to put a storm of complexity into a fairly solid box, and say: look, you can now surf on it! That’s particularly true for an app such as iObserve which has more than 80k lines of code (and many custom connectors to crazy webservices, yes, I’m looking at you JPL horizons…).
The journey is far from finished!
The 1.4.1 has just been submitted to the Store. Should be there in ~5 days. (http://appreviewtimes.com). It fixes the tiny but painful bug on Mavericks.
[Update:] The v1.4.1 is now available, 11 hours after the expedited review I requested this morning. Nice!
It has been reported to me that there is an annoying bug for Mavericks users with the latest iObserve version 1.4.0. The « New Object » sheet doesn’t appear at all. Sorry for that! I am currently fixing it and will push it ASAP to the App Store for review. In the meantime, you can use the ‘Import from list’ feature, in the ‘File’ menu (I know, this isn’t as good… Pro tip: Did you know that by alt-clicking on « New Object » you were actually opening the ‘Import from list’ sheet?…
I just discovered that cfitsio has troubles opening files that have a whitespace in their path. In that case, QLFits3 is unable to open the file! I’m on it!