I’ve updated the ‘development’ version of the Community CPS
Its installed into Program files x86 by default
It no longer uses setup.ini to store the settings as these are now stored in the windows registry as they should be retained when updating to newer versions (though this doesn’t always seem to work, and currently I”m not sure why)
If you want to install elsewhere that is also possible and if you want to use setup.ini I’ve added a “Portable” installation option in the installer which uses setup so the CPS should be able to run on a memory stick etc for use where perhaps you use it at work and can’t install programs.
I got fed up with having to open my code plug each time, so it now remembers the last codeplug you saved and will re-open that one again when the CPS opens.
if you want a blank codeplug, you can still press the New codeplug button or select it from the menu
I’ve changed the version number from 2.0.5 to 3.0.6 as Radioddity now seem to be using the same version number for the CPS and the firmware, so it makes sense to change my version in preparation for when Radioddity finally release firmware 3.1.x (and the matching 3.1.x CPS)
I’ve fixed a bug where the development version ‘Build’ date was not actually the date I built the exe but it was using the current date, which was mistake in my code. I’ve now switched this to using the built in version numbering supplied with the Visual Studio development environment which and the build version will appear as 1.0.xxx.yyy. (xxx is the number of days since 01/01/2000 . Ignore the yyy part as I think its the number of seconds since midnight divided by 2)
I’ve also changed the title bar on the CPS to show the full path of the file that is currently loaded, except for when it has no user file loaded (and has Default.dat loaded)
I also got fed up with having to agree to terms each time the CPS opens, so if you agree the terms this value is now saved and it won’t ask again.
One other change which has been in the code for some time is that it is possible to perform a file association between the .dat file or a .g77 (I made up a new file extension ;-), to the CPS.
I’ve not been able to get the installer to automatically setup the file association, but you can manually do this in Windows and it should work if you double click on a .dat to open the CPS and load that file
I also made some changes ‘under the hood’, so that the structures that store the Rx Group Lists are in separate code source files, as I hoped that when Radioddity release a final version of 3.1.x, which I presume will have the changes to Rx Group Lists, I may be able to allow the CPS to handle both the old and new structures.
However it looks like this won’t be possible, because the code is not structured to allow this, and would require a major re-write to make that work.
So when CPS 3.1.x is finally released by Radioddity, I’ll probably have to do a more hack solution where the data for the Rx Group list pre-processed if the codeplug from 2.0.5
I think its fairly stable,and if you’ve not updated for a while you may notice other changes which I did a few weeks ago, including the ability to update your Digital Contacts from the Ham-digital.org “Last heard” database etc.
I’d appreciate if anyone can test and let me know if they experience any problems
BTW. I’ve left the old installer on github https://github.com/rogerclarkmelbourne/radioddity_gd-77_cps2.0.5/raw/development/installer/RadioddityCPS2.0.5CommunityEditionInstaller.exe
In case anyone has issues with this one.