Feedback for NG 1.0.8

[AL7EK]

Hello Tom,

I am a new user of RumLogNG and I really like it!!! I first downloaded NG 1.0.7. I had a few problems with it, then I noticed you have made a new version 1.0.8 so I downloaded it and just completed a quick test of it.

As with the previous version, I am having a few problems with 1.0.8. Keep in mind I am a new user so some of these problems may be due to my inexperience with RumLogNG. I am running on an iMac with 10.9.5.

1. When I upgraded from 1.07 to 1.0.8 I notice several configuration entries were not saved. For example, my name and call were not saved but my user name for DX Cluster GB7MBC was saved. In general I have a lot of trouble getting my configuration to be saved. For example if I enter my LoTW user name and password, then try to enter my eQSL username, the LoTW username disappears.

2. Since I am a new user, my logbook has no QSOs or QSLs in it. I am having trouble getting any of my past ones in it. I have downloaded an ADIF file from eQSL of my past QSLs. That is stored on my desktop as eQSL.adi. When I do Logbook/Import ADIF, I get a message “Please disconnect from dx cluster first. Possible database conflict during background operation.”. So I disconnected from the cluster. Then I retried the Import ADIF. I still get the message. If I click through the warnings and try to import the eQSL.adi file, I find that it is grayed out on the menu that shows the list of files. This happens even if I restart and try without ever connecting to the cluster. I have renamed the file to eQLS.adif and that didn’t help.

3. When I restarted, the app still didn’t remember the path to the log file.

4. When I try QSL/LoTW In, I get a window with a list of QSLs in it. They are all red. The window shows that the QSos are not in the log. When I click Close, they are not added to the log. The same thing happens when I click QLS/eQSL In. If I click Read data from eQSL or Read data from LoTW, those QSLs disappear. I am not certain how to get them back. Because of this problem as well as problem number 2, I am unable to get any past QSOs into my log.

5. When I close all the windows, the RUmLogNG icon is left in the doc with the active indicator lit, but it cannot be used to gain access to the program. I suggest that it be deactivated when the main window is closed. Also when the main window is closed, maybe all other windows should be closed although other users may prefer to keep other windows up even when not logging.

6. Just a small thing, but the clock on the main screen for me shows “ 4:44:36” and then only a small part of the next characters which I think might be “AM”. It would help if you could make the time label a little wider.

7. Sometimes the Connect button on the DX-Cluster Terminal window is grayed out when the terminal is not connected. I can get this to happen if I close the window without disconnecting first. It appears the only way to recover from this is to close the app and restart.

Tom, please let me know if some of these problems are caused by my inexperience with your app. I suspect they are. Or if you need me to perform additional testing or send you screen shots, I will be happy to do either.

Also, do you have any interest in anyone helping you with your app. I am a java and .Net developer and I would love to have a reason to learn Xcode and Cocoa.

Best wishes,

Clark, AL7EK

[DL2RUM]

Hi Clark,

thanks for your observations. There are some glitches, but it seems always for 10.9 users. I don't have this old system here. The problems are different slightly, but start always with "Preferences will not be saved".

Please try the following:

• Make sure you are using the latest version 1.0.8
• Quit RUMlog
• In Finder go to your Home/Library/Containers
• Delete the whole folder de.dl2rum.RUMlogNG
• Reboot the Mac
• Restart RUMlog

Normally the Library folder is hidden, so you could use the Finder Menu-->Go-->Go to folder and enter ~/Library/Containers


2. In fact, the terminal window should be closed during an ADIF import, I changed the given message in that case. The file to import must have the extension *.adi or *.adif
In the finder make sure, it is not named like file.adi.txt. Hopefully there isn't another 10.9 bug.

4. This is not the way it works. RUMlog don't import any QSOs after a LoTW or eQSL download. It is used to change the QSL status of a given QSO only! Therefore the QSO must be in the log already.

5. When all windows are closed, RUMlog is still active. Activate the application in the Finder and use the Window menu to reopen windows.

6. Well, an unforeseen mistake for users with a 12hour clock. I have to fix.

7. When the Connect button is inactive, the terminal tries in this moment to connect to a server. This may take up to a minute.

[AL7EK]

Tom

I will try the things you mentioned and I'll report back after I retest. Basically it sounds like I should upgrade to 10.10. I usually wait a bit for all the bugs to get fixed and I think I have waited too long.

With respect to the time, can you offer an option to show the time as 24 hour in your windows no matter what the time is on the system? I keep my system time set to Central US time and show it in 12 hour format. I would love it if the logger showed UDT in 24 hour format. That would save some space also so you wouldn't have to resize the label.

Good to know how the other things work also. I think I will be able to get the ADI file entered now that I know the terminal must be closed. Question though, what does the terminal window have to do with the log database? ... oh, I know...it has the database opened so it can determine whether the station is in the log or not and the database is not multi-user.

Clark

[DL2RUM]

Clark,
due to a fatal error on my side, the latest downloadable version was not fixed for 10.9 as I hoped! Please use this version (Build 39) now: http://dl2rum.de/RUMlogNG/RUMlogNG.zip

To show a 24 hour clock, you have to change the system settings. Before I can make a new time read out, I have to fix other issues.

[AL7EK]

Tom

I am now using 1.0.9. I was able to import an adif file. I did notice something you might want to look at. When I tell the log view to view all years, it appears to only show logs for 2015. It does not show logs for 2014 unless I select 2014.

I think I am going to update to 10.10. Do you have any interest in me testing anything with 10.9 before I do so?

Clark

[DL2RUM]

Please note, when you have selected 2014, you probably selected the year in the search options. On the right hand side below the "Save" button is a popup for the selection of shown QSOs. Select "All QSOs". Per default it is set to show few QSOs only. This is due to performance reasons, when you have some 10.000 QSOs in the log.