www.dl2rum.de

Hello! I very much enjoyed using the previous version of RUMlog, I found it to be very thorough and easy to use once I got the hang of it.
I downloaded version NG 1.0.7 a few weeks ago and have been using it quite regularly. There are a few things about it that did not work the way I would have expected. I will outline those items here in case others are experiencing the same. Thank you DL2RUM for your hard work! I hope that you find this feedback informative. Let me know if you need any additional information.

I'm running OS X 10.9.5 on a MacPro.

• When using the search at the bottom to filter QSO, and then editing any QSO from the search result view, my changes were not saved once the search results were cleared. I was adding the W designation to the QSL box. Upon further testing, note that editing any data in a QSO that is shown as a search result doesn’t actually save once you clear the search.
• I highlighted 3 QSO and double clicked to EDIT. RUMlogNG went halftone color (like normally when editing QSO) except that no edit screen shows and the interface is no longer usable. Had to force quit application to restart.
• Moving window causes characters in log to disappear or format oddly screenshot: https://www.dropbox.com/s/8p4l93iu705jg ... 5.png?dl=0
• QRZ XML call sign data look-up does not appear to load any data in the QSO window or the sidebar. I’ve double checked my QRZ.com credentials and that my XML query functionality is working using an alternate app
• First launch app, doesn’t show any of the contacts in my log, i have to pull down the view bar to show 500 QSO’s for anything to show up. Not expected behavior.
• When printing QSL Out labels, the equipment line printed left justified even though my preference setting is set to Center justified

Thanks for hearing my feedback. If you need more information, please let me know!

73 de KK6FNK

Thanks for your excellent report.

When using the search at the bottom to filter QSO, and then editing any QSO from the search result view, my changes were not saved once the search results were cleared.

Confirmed. In fact, the changes are saved, but are not shown in the log until a reload or restart.

When printing QSL Out labels, the equipment line printed left justified even though my preference setting is set to Center justified

Confirmed.

QRZ XML call sign data look-up does not appear to load any data in the QSO window or the sidebar.

Any error messages? What happens? Blank table in the side window? Can you check Console for errors please?

The other problems may be caused by 10.9. in conjunction with RUMlogNG. With the great help of Charles, K4ZRJ we tracked down the problem. He was unable to use the application since it was impossible to create or open a new log file.

I will release an updated version soon.

See here: http://dl2rum.de/forum/viewtopic.php?f=10&t=655

Tom, you're most welcome for the feedback! I work in a type of development (Blu-ray Discs) and we always appreciate notes when we can get them.

QRZ Lookup Error:

Any error messages? What happens? Blank table in the side window? Can you check Console for errors please?

Here is a screenshot of what I see in RUMlogNG:
https://www.dropbox.com/s/e6d8z6gjhpisg ... 5.png?dl=0

These are the errors in Console:
https://www.dropbox.com/s/x965802hm94ay ... 9.png?dl=0

I highlighted 3 QSO and double clicked to EDIT. RUMlogNG went halftone color (like normally when editing QSO) except that no edit screen shows and the interface is no longer usable. Had to force quit application to restart.

This is resolved in Ver 1.0.8 ! Thanks!

Moving window causes characters in log to disappear or format oddly

EDIT: Still observing this behavior in 1.0.8


Thanks for your help!

Due to the message inspector window I can't see the most important entry: some with "... of Object xxx is NIL" Disregard the incorrect entitlements messages.

DL2RUM wrote:Due to the message inspector window I can't see the most important entry: some with "... of Object xxx is NIL" Disregard the incorrect entitlements messages.

Sorry there, I wasn't sure what data was relevant.

3/7/15 7:45:33.105 AM RUMlogNG[1404]: *** -[NSKeyValueSlowMutableArray count]: value for key qrzQueryResultArray of object 0x7fa824006800 is nil

3/7/15 7:45:33.106 AM RUMlogNG[1404]: (
0 CoreFoundation 0x00007fff8ce5325c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x00007fff88e9fe75 objc_exception_throw + 43
2 CoreFoundation 0x00007fff8ce5310c +[NSException raise:format:] + 204
3 Foundation 0x00007fff8a2781eb -[NSKeyValueSlowMutableArray _raiseNilValueExceptionWithSelector:] + 111
4 Foundation 0x00007fff8a210688 -[NSKeyValueSlowMutableArray count] + 83
5 CoreFoundation 0x00007fff8cd6e62c -[NSMutableArray addObjectsFromArray:] + 540
6 RUMlogNG 0x0000000104e72f0c RUMlogNG + 130828
7 Foundation 0x00007fff8a1c17ce __NSThreadPerformPerform + 229
8 CoreFoundation 0x00007fff8cd845b1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
9 CoreFoundation 0x00007fff8cd75c62 __CFRunLoopDoSources0 + 242
10 CoreFoundation 0x00007fff8cd753ef __CFRunLoopRun + 831
11 CoreFoundation 0x00007fff8cd74e75 CFRunLoopRunSpecific + 309
12 HIToolbox 0x00007fff87ff6a0d RunCurrentEventLoopInMode + 226
13 HIToolbox 0x00007fff87ff6685 ReceiveNextEventCommon + 173
14 HIToolbox 0x00007fff87ff65bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
15 AppKit 0x00007fff912c924e _DPSNextEvent + 1434
16 AppKit 0x00007fff912c889b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
17 AppKit 0x00007fff912bc99c -[NSApplication run] + 553
18 AppKit 0x00007fff912a7783 NSApplicationMain + 940
19 libdyld.dylib 0x00007fff895785fd start + 1
)