Hi Len,
Do you have any plans to add a color specification for a manual spot?
Hi Martin, I hadn't thought of that, but let me take a look at it. I am guessing that it would not be too difficult.
Hi Martin, thanks for the suggestion! I am nearly done with the code to specify spot color and spot background color. I have overall spot colors working and will now code up the ability to control each spot individually.
So for those who want all their spots to look the same, they just set the default. Any individual spots can then be set to override the default for those who want a more custom look (red on yellow for band-edges, for example).
I should have something ready later today or maybe tomorrow.
The available colors are from the Windows .net palette (see link, below). There are 141 named colors available, so I am not going to include the complication of a color mixer.
Colors Class (System.Windows.Media) | Microsoft Learn
You will specify them by name. For example to set the default:
SpotColor: YELLOW SpotBackColor: Transparent
On individual spots:
SpotColor=RED SpotBackColor=YELLOW
Let me know if you have any other thoughts on this.
Well, that was easier than I expected... I have a bit more testing to do, but I should be able to put this new version on GitHub later today. Here is my first test:
Len
How about a "Spot Life" setting?
Oh, and a "Clear All Spots" button.
Another approach for building the necessary spot data. Instead of pulling the data from the memory backup file, issue the "sub memory all" command. The command's response will be a list of all memories, along with all memory settings. Build your spot commands from this list.
Send the sub memory all command on startup of the spot application, to update the memory data.
Alan. WA9WUD
Hi Alan, These spots are designed to be "permanent". They are not DX spots, but instead, are intended to mark repeater frequencies, nets, band edges and that kind of thing so spot life is not really appropriate here.
Clear All Spots is already taken care of on the Flex Spot Settings page, so I won't duplicate it here.
My app does not pull data from the backup file, it comes directly from the radio. Since I am using C# and FlexLib under .net, the "sub memory all" command is done on my behalf when I execute the following statement:
radio.MemoryAdded += new Radio.MemoryAddedEventHandler(_thisRadio_MemoryAdded);
_thisRadio_MemoryAdded is a subroutine that I wrote that populates my data array of spot info so that I have the everything necessary to change mode and/or repeater options as spots are clicked. The full source code is on my GitHub site if you are interested in how this works.
Hi Len,
You're very efficient.
Thanks you very much for taking my suggestion.
73, Martin VA2PX
FlexRepeaterSpots V1.06 is now available on GitHub:
// *********************************************************************** // V1.06 // Increased the max number of spots from 100 to 400 // Added code to be sure max spots is not exceeded // Added ability to set default spot color and spot background color // Added ability to set text and background colors on individual spots // ***********************************************************************
Thanks to Martin, VA2PX for the spot color suggestion!
The default colors can be set using these Config.ini entries (default is Yellow and Transparent):
SpotColor: YELLOW SpotBackColor: Transparent
Each Spot: line in Config.ini can have either, both or neither of SpotColor= and SpotBackColor=.
SpotColor=RED SpotBackColor=YELLOW
On all of these parameters, case is not important.
I finally finished the FlexRepeaterSpots user manual. It is on the GitHub site shown in the previous post, above. I also updated the V1.06 release to include it there.
Here is the intro from that document:
FlexRepeaterSpots V1.07 is now available on GitHub:
// *********************************************************************** // V1.07 // Added SpotMemColor: and SpotMemBackColor: (Thanks Bret, WX7Y!) // ***********************************************************************
Bret, WX7Y suggested that memory spots have their own color scheme. Good idea Bret! Just add the following lines to your Config.ini file.
SpotMemColor: Yellow SpotMemBackColor: Transparent
Make the colors anything you like from this list:
Colors Class (System.Windows.Media) | Microsoft Learn
The default colors are the same as for regular (non-memory) spots, so if you leave these lines out of your Config file, you will get Yellow and Transparent.
Thanks again for the idea Bret, and I hope this is what you were looking for.
Great Job Len and works great.
Once I got the Color combinations I like and could see without straining my eyes
Anyway Thanks Len for all your hard work
73
Bret
WX7Y
Thanks Bret, I appreciate it!
Hi Len, just have a question, Is there a limit to how may Spots you can have?
If there was a limit I just wanted to make sure I wasn't getting close.
73
Bret/WX7Y
Hi Bret, as of V1.06 you can have up to 400 spots. DX spots or spots from any source other than FlexRepeaterSpots don't count toward the 400.
If you find that you are getting close to that maximum, let me know and I will make it bigger. It is a very easy change to implement.
If you are asking about limits, you must be getting some good use out of the utility!
Ok I think that should be plenty for about everyone I imagine
@Rich McCabe Hi Rich, just checking in to see if you were able to get FlexRepeaterSpots downloaded and working.
Are there any alpha/beta testers testing the 8000 series that can try Flex Repeater Spots? I don't need an exhaustive test, I just need to know that the executable runs and that the basic functionality is there.
Release FlexRepeaterSpots V1.07 · KD0RC/FlexRepeaterSpots
I doubt that the API and FlexLib changed much, but I would feel better knowing that it still works.
FlexRepeaterSpots V1.08 is now available on GitHub:
Release FlexRepeaterSpots V1.08 · KD0RC/FlexRepeaterSpots
// ***********************************************************************
// V1.08
// Added the ability to automatically fill the N3FJP callsign box with a
// clicked DX spot. Non-DX spots will not go to the log.
// Added a menu option to turn N3FJP callsign population on and off
// Added Config.ini item to allow defaulting N3FJP population on or off
// Changed to allow Squelch and Squelch Level to be set on non-FM mode spots
// ***********************************************************************
This release adds automatic posting of a DX spot callsign directly into the Callsign box in the N3FJP series of loggers. Just click the spot and it appears in your logger. It can be turned on and off using a menu item. Non-DX spots (i.e. spots generated by this utility) are not posted to N3FJP.
With this new feature, it becomes more usable, even if you do not use it for setting repeater options. It can be left on in the background; there is seldom need to bring this main screen to the foreground.
The N3FJP API needs to be enabled. Go to Settings, Application Program Interface (API) and check the TCP API Enabled box. Make sure that the Port is set to 1100.
If you give this a try, let me know how it goes. My first spot to N3FJP was W1AW!
The Flex Repeater Spots User Manual has been updated. Here is a link:
FlexRepeaterSpots/FlexRepeaterSpots User Manual.docx at main · KD0RC/FlexRepeaterSpots
To get the manual, click the little download icon (see example below):
Has anyone else tried it yet?
FlexRepeaterSpots V1.09 is now available on GitHub:
Release FlexRepeaterSpots V1.09 · KD0RC/FlexRepeaterSpots
// ***********************************************************************
// V1.09
// If a restart is needed due to loss of connection to N3FJP, pop screen
// to top of other apps so that the Restart button can be pressed
// Fixed bug where Squelch state is turned off and level is zeroed out
// when not specified in the Config.ini file
// Removed 400 spot limit (using List instead of Array)
// Minor code reorg, clean up and small bug fixes
// Added info to the About box
Just minor things this go-round.
Thanks to Rich, KD0ZV for uncovering a bug in FlexRepeaterSpots. The problem occurs if there is no trailing space behind the name of the license class in the MyLicense parameter ("MyLicense: Extra " = OK. "MyLicense: Extra" = Error). That is now fixed in version 1.10 Beta 1.
Several people have noted that you have to uninstall the previous version before installing the new one or you get an error. I am still working on that one, so here is a beta version with the MyLicense problem fixed, but you will still need to uninstall the previous version before installing this one. Please give it a shot and let me know how it goes.
// ***********************************************************************
// V1.10
// Fixed bug where the app crashes when MyLicense is set at end of file
// Added error checking to license classes
// ***********************************************************************
FlexRepeaterSpots V1.10 is now available on GitHub:
Release FlexRepeaterSpots V1.10 · KD0RC/FlexRepeaterSpots
// ***********************************************************************
// V1.10
// Fixed bug where the app crashes when MyLicense is set at end of file,
// end of line or no trailing space found
// Added error checking to license classes and Config file parsing
// ***********************************************************************
This release is the same as the beta version released above, but with a bit more clean-up and error checking.
Thanks to Bret, WX7Y for helping me to debug an issue with the V1.10 release! The issue was an expired certificate. Here is a link to the utility (same version number - the code did not change). The zip file has the word NEW in it to distinguish it from the previous one.
Release FlexRepeaterSpots V1.10 · KD0RC/FlexRepeaterSpots
Please give this a try and let me know of any issues.
Note that you may need to uninstall the previous version before installing the new one. It should be an uninstall, not a deletion of any folders or files.
Well, no sooner did I post the above, than I discovered the proper way to do a Windows install from Visual Studio… Windows programmers - don't laugh when I describe this.
I was using the basic publish feature of Visual Studio, not realizing that you have to add a project to the desired project that contains the Windows installer (not exactly intuitive…). Works slick once you know how it operates, but you have to know that it exists and that you have to add it to your project.
In any event, I have once again replaced the setup file on GitHub (same link as above). This version will automagically delete the previous version when new versions come out. You may still need to delete the previous version this time, as it was installed differently. Going forward, just do the install and it will prompt you:
Just select the Repair option and it will re-install whatever is needed from the new release.
Len, I spoke to soon I was reinstalling an older version and not the latest, I am still getting the install error on my machine that has had FlexRepeaterSpots on it before, I did an uninstall before I tried to install the latest release this evening.
I get this error
and the Error Log details is here
I had to install it on my laptop for it to load maybe it doesn't like my download folder on drive D: instead of C: 73
Bret WX7Y
Hi Bret, I believe that is the old security certificate problem. I just did some more testing using my old laptop and think that I have that all worked out now.
Here is the latest version. To install, you will need to uninstall the old version first. I am on the brink of solving the automatic uninstall problem, but for now, a manual uninstall is needed.
Release FlexRepeaterSpots V1.10 · KD0RC/FlexRepeaterSpots
Note that this is software version 1.10, but the setup is version 1.10A so that you know that you have the right one when you download from GitHub.
Hi Len, WORKS so far removed the old Ver 1.10 and installed 1.10A from my "Downloads" folder on Drive "D" (This is where it was Broken before) and then after making sure it was working I uninstalled it, Un installed just fine, then I reinstalled 1.10A and that worked A-OK with NO issues.
Wow thanks for your hard work on the not so common Windows installer bug. I hope I was a little help.
73's and have a great evening
Bret WX7Y
Thanks Bret, I REALLY appreciate all of your patience and help, it made a huge difference! My old mainframe accent (Fortran, COBOL, PL/I) really comes out when I do Windows programming in C#…
Now I need to do the same thing with my Flexicraft Utility.
