One button configuration save
If you want a new feature or a change to the software then add your request here.One button configuration save
how about feature that at the click of a button a text or xml file so that the whole configuration is easily attached to a post.
Re: One button configuration save
OK, repeated with proper grammar!
how about a feature that at the click of a button generates a text or xml file so that the whole configuration is easily attached to a post.
how about a feature that at the click of a button generates a text or xml file so that the whole configuration is easily attached to a post.
Re: One button configuration save
It is not often needed. Usually the unedited and not accidentally resized screen capture of SDRC is sufficient. The picture usually easier for Simon to read than the text.
{o.o}
{o.o}
Re: One button configuration save
How long does it normally take for a post to appear?
I made two post Tuesday evening, and they have not appeared yet.
I made two post Tuesday evening, and they have not appeared yet.
Re: One button configuration save
You were sent notifications that those two posts were not approved on Tuesday.
--
Mike
Mike
Re: One button configuration save
Post disapproved: "One button configuration save"
Reason: The reported message does not fit into any other category, please use the further information field. You were informed of Simon's *preferred* methods. As such, this post is more argumentitive than anything else..
Tue Jan 14, 2025 8:02 pm
I was informed of Simon's preferred method?
How?
By another member's post stating what he thought Simon's preference was?
I didn't see Simon express an opinion one way or another.
I thought this forum was a place where opinions could be shared and discussed.
I thought I would get a better response than = it's always been done that way!
Reason: The reported message does not fit into any other category, please use the further information field. You were informed of Simon's *preferred* methods. As such, this post is more argumentitive than anything else..
Tue Jan 14, 2025 8:02 pm
I was informed of Simon's preferred method?
How?
By another member's post stating what he thought Simon's preference was?
I didn't see Simon express an opinion one way or another.
I thought this forum was a place where opinions could be shared and discussed.
I thought I would get a better response than = it's always been done that way!
Re: One button configuration save
You already have a one button configuration save. Exit the program. The X upper right on the main window does this in one click. Next time you open this identity it will have that configuration saved. The program is not designed to permit full configuration changes while running live - a feature of the base classes for the GUI in the program. I've run into this playing with a fancy bunch of windows with Microsoft Foundation Classes, from which Simon's GUI is derived with improved drawing facilities.
What good is it to save a configuration if you cannot reload it?
There is a fugly option - exit the program. Make a copy of the configuration you like from the SDR-Radio (v3) folder in your AppData\Roaming, %AppData%, folder. Then each time you run the program do it from a script that copies this copy you made in over the last saved data for that identity.
Or do you mean favorites or memories? If so what should the mind reader presume you mean to use for a name for the data you saved? An automatic name is required if you want one button press to save a new favorite, for example.
Simon has remarked in the test build forum that he has his next year of development work laid out with no room for additions.
(And personally, I am troubled by people demanding their favorite addition in a free program. Requesting, yeah. Simon does keep a list of requests. Your message's tone hits MY mind as a demand. YMMV, of course.)
{^_^}
What good is it to save a configuration if you cannot reload it?
There is a fugly option - exit the program. Make a copy of the configuration you like from the SDR-Radio (v3) folder in your AppData\Roaming, %AppData%, folder. Then each time you run the program do it from a script that copies this copy you made in over the last saved data for that identity.
Or do you mean favorites or memories? If so what should the mind reader presume you mean to use for a name for the data you saved? An automatic name is required if you want one button press to save a new favorite, for example.
Simon has remarked in the test build forum that he has his next year of development work laid out with no room for additions.
(And personally, I am troubled by people demanding their favorite addition in a free program. Requesting, yeah. Simon does keep a list of requests. Your message's tone hits MY mind as a demand. YMMV, of course.)
{^_^}
Re: One button configuration save
I apologize if I upset anyone - it was not my objective.
But I maintain the feature I was describing (one button to save the configuration as a txt or xml file that could be copied and pasted into a post) might be useful.
I think some users might find it useful as well - no need to guess what screens to copy and paste into a post.
I would be interested in Simon's opinion.
Also, I don't think I was demanding anything.
I said in my original post how about a feature that at the click of a button......
I would be interested in what other users think as well.
BTW, this is a common feature in the IT industry, like Cisco.
I don't think I'll have much more to say on this topic.
I hope I have made it clear what I was suggesting and probably won't have much more to say on this topic.
But I maintain the feature I was describing (one button to save the configuration as a txt or xml file that could be copied and pasted into a post) might be useful.
I think some users might find it useful as well - no need to guess what screens to copy and paste into a post.
I would be interested in Simon's opinion.
Also, I don't think I was demanding anything.
I said in my original post how about a feature that at the click of a button......
I would be interested in what other users think as well.
BTW, this is a common feature in the IT industry, like Cisco.
I don't think I'll have much more to say on this topic.
I hope I have made it clear what I was suggesting and probably won't have much more to say on this topic.
Re: One button configuration save
Um, perhaps defining what you consider to be the configuration might clear things up.
The full SDRC identity configuration is a largish set of files. Ignoring what is in the registry look in "%AppData%\SDR-RADIO.com (V3)\Console". Each folder is a radio configuration, less, I believe, window locations. The window locations are in the registry, I believe.
Now, do you want that whole thing? Do you want a subset? If so define it. If you have several receivers active, which one is selected or are all selected. It's a really tough job to guess what aspect of all that you want. MAYBE you want the subset that is in the "SDR-Favourites_000.xml" file individual entries. That might be easy to arrange. But, some automatic file naming would be needed. I suppose a file named after the date and time it was created would not do. But that might need to be part of the file name to avoid collisions. I suspect something of this sort if what you have in mind. Even the SDR-FavDefault_000.xml is a large file. It includes all the gain settings etc. Maybe a subset of that?
{o.o} (Just peeping over the fence to note this is not really a simple obvious thing to do. SDRC is BIG.)
The full SDRC identity configuration is a largish set of files. Ignoring what is in the registry look in "%AppData%\SDR-RADIO.com (V3)\Console". Each folder is a radio configuration, less, I believe, window locations. The window locations are in the registry, I believe.
Now, do you want that whole thing? Do you want a subset? If so define it. If you have several receivers active, which one is selected or are all selected. It's a really tough job to guess what aspect of all that you want. MAYBE you want the subset that is in the "SDR-Favourites_000.xml" file individual entries. That might be easy to arrange. But, some automatic file naming would be needed. I suppose a file named after the date and time it was created would not do. But that might need to be part of the file name to avoid collisions. I suspect something of this sort if what you have in mind. Even the SDR-FavDefault_000.xml is a large file. It includes all the gain settings etc. Maybe a subset of that?
{o.o} (Just peeping over the fence to note this is not really a simple obvious thing to do. SDRC is BIG.)
Re: One button configuration save
BTW - I have a couple requests in with Simon. They seem simple. But he tells me they would not be simple to implement because of the way SDRC is built inside. My guess is that it is in the million line class of projects.
{O.O} (Wide eyed)
{O.O} (Wide eyed)