I've been using RUMlog and RUMlog2Go for some time now, sharing the log via Dropbox. Everything works just fine.
Only glitch I noticed is that new QSOs added on RUMlog2Go are shown in RUMlog with a different date format, so I end up with something like this:
Screen Shot 2013-07-03 at 6.41.11 PM.png (39.2 KiB) Viewed 3959 times
Screen Shot 2013-07-03 at 6.41.11 PM.png (39.2 KiB) Viewed 3959 times
Yes, I'm aware of this situation.
On the iPad the date format is specified in your system settings. In RUMlog for Mac, you can select a format within the program itself. You should change one setting. But one problem will remain: The limiter will differ. On my mac it shows 02-07-2013, logged on the iPad it shows 02.07.2013
Maybe RUMlog could re-format dates according to its settings for display in the QSOs list, regardless of the actual data format. In fact RUMlog2Go display of dates fields is always consistent with its local format.
Dev note: I see that the date field in the SQlite table is varchar, and saved with a format that depends on the settings of the app that created the record. Wouldn't it be a good idea to always use a fixed format for this field in the database (like yyyy-mm-dd, for example)?
The date and time is stored in a standard sql format YYYY-MM-DD HH:MM:SS as well. The other saved (user) format was introduced due to performance issues. This should not be a problem today. I will try it out.
