Re: [Flexradio] Editing the database wasn't what I wanted originally anyway
It's probably not that hard to implement a feature that would do a lookup of entries from the memory table. Each time you change the frequency the software looks for a match in the memory table and if it finds one it will display memory table data instead of band text data. Would probably hog system resources though. Just a thought... Edwin MarzanAB2VW From: [EMAIL PROTECTED] To: [EMAIL PROTECTED]; flexradio@flex-radio.biz Date: Wed, 23 Jul 2008 15:46:16 -0400 Subject: Re: [Flexradio] Editing the database wasn't what I wanted originally anyway Alan, If you read my reply to Chuck, AA5J, then you will see that the way the database software are structured, clicking on a frequency to add a custom label would not be an easy feature to implement. Each frequency does not exist in the database as an entity by itself, but rather the spectrum is broken down into frequency ranges that have a common label (80M CW, 40M SSB, etc.). In order to label a specific frequency, you have to replace 1 record in the database with 3. This can be done of course, but programmatically it is difficult somewhat dangerous to do as an automatic process. 73, Ray, K9DUR___ FlexRadio Systems Mailing List FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archives: http://www.mail-archive.com/flexradio%40flex-radio.biz/ Knowledge Base: http://kb.flex-radio.com/ Homepage: http://www.flex-radio.com/ _ Keep your kids safer online with Windows Live Family Safety. http://www.windowslive.com/family_safety/overview.html?ocid=TXT_TAGLM_WL_family_safety_072008 ___ FlexRadio Systems Mailing List FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archives: http://www.mail-archive.com/flexradio%40flex-radio.biz/ Knowledge Base: http://kb.flex-radio.com/ Homepage: http://www.flex-radio.com/
Re: [Flexradio] Editing the database wasn't what I wanted originally anyway
Alan, If you read my reply to Chuck, AA5J, then you will see that the way the database software are structured, clicking on a frequency to add a custom label would not be an easy feature to implement. Each frequency does not exist in the database as an entity by itself, but rather the spectrum is broken down into frequency ranges that have a common label (80M CW, 40M SSB, etc.). In order to label a specific frequency, you have to replace 1 record in the database with 3. This can be done of course, but programmatically it is difficult somewhat dangerous to do as an automatic process. 73, Ray, K9DUR ___ FlexRadio Systems Mailing List FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archives: http://www.mail-archive.com/flexradio%40flex-radio.biz/ Knowledge Base: http://kb.flex-radio.com/ Homepage: http://www.flex-radio.com/
Re: [Flexradio] Editing the database wasn't what I wanted originally anyway
Yes, I can see that now, Ray. Oh well... 73 Alan NV8A On 07/23/08 03:46 pm Ray, K9DUR wrote: Alan, If you read my reply to Chuck, AA5J, then you will see that the way the database software are structured, clicking on a frequency to add a custom label would not be an easy feature to implement. Each frequency does not exist in the database as an entity by itself, but rather the spectrum is broken down into frequency ranges that have a common label (80M CW, 40M SSB, etc.). In order to label a specific frequency, you have to replace 1 record in the database with 3. This can be done of course, but programmatically it is difficult somewhat dangerous to do as an automatic process. ___ FlexRadio Systems Mailing List FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archives: http://www.mail-archive.com/flexradio%40flex-radio.biz/ Knowledge Base: http://kb.flex-radio.com/ Homepage: http://www.flex-radio.com/
Re: [Flexradio] Editing the database wasn't what I wanted originally anyway
Ray or anyone else, You appear to be quite familiar with the structure of the database. I have been looking at altering a behavior of the band stacking registers and I need some help. On 60 meters, the frequencies are fixed. Once one is selected, you can tune it normally but reselecting it returns you to the prestored frequency and mode etc. It acts as a kind of memory that is reminiscent of Kenwood memory operation and I like the way it works. On any of the other bands the frequency is not fixed. If you tune to another frequency it remembers the last frequency and mode, thus bandstacking. That function must be in some other part of the code because it's not in the database, at least that I can find. I'd like to be able to store a fixed frequency in the database and when I select the band, I could cycle through several prestored frequencies in the same manner as is done on 60 meters, instead of the stacking registers which change. I don't care if the band stacking function is compromised. Since the code is already there, this must be a simple request but I am going broke on coffee trying to find it. Ideas? Thanks -- Larry W8ER Ray, K9DUR wrote: Alan, If you read my reply to Chuck, AA5J, then you will see that the way the database software are structured, clicking on a frequency to add a custom label would not be an easy feature to implement. Each frequency does not exist in the database as an entity by itself, but rather the spectrum is broken down into frequency ranges that have a common label (80M CW, 40M SSB, etc.). In order to label a specific frequency, you have to replace 1 record in the database with 3. This can be done of course, but programmatically it is difficult somewhat dangerous to do as an automatic process. 73, Ray, K9DUR ___ FlexRadio Systems Mailing List FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archives: http://www.mail-archive.com/flexradio%40flex-radio.biz/ Knowledge Base: http://kb.flex-radio.com/ Homepage: http://www.flex-radio.com/ ___ FlexRadio Systems Mailing List FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archives: http://www.mail-archive.com/flexradio%40flex-radio.biz/ Knowledge Base: http://kb.flex-radio.com/ Homepage: http://www.flex-radio.com/
Re: [Flexradio] Editing the database wasn't what I wanted originally anyway
The algorithm itself locks it in that way. Take a look at private void SaveBand() in console.cs under the case Band.B60M. You could just remove the frequency qualification there and I think it would work then. ;) Eric Wachsmann FlexRadio Systems -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Larry W8ER Sent: Wednesday, July 23, 2008 3:28 PM To: Ray, K9DUR Cc: 'Flex Group' Subject: Re: [Flexradio] Editing the database wasn't what I wanted originally anyway Ray or anyone else, You appear to be quite familiar with the structure of the database. I have been looking at altering a behavior of the band stacking registers and I need some help. On 60 meters, the frequencies are fixed. Once one is selected, you can tune it normally but reselecting it returns you to the prestored frequency and mode etc. It acts as a kind of memory that is reminiscent of Kenwood memory operation and I like the way it works. On any of the other bands the frequency is not fixed. If you tune to another frequency it remembers the last frequency and mode, thus bandstacking. That function must be in some other part of the code because it's not in the database, at least that I can find. I'd like to be able to store a fixed frequency in the database and when I select the band, I could cycle through several prestored frequencies in the same manner as is done on 60 meters, instead of the stacking registers which change. I don't care if the band stacking function is compromised. Since the code is already there, this must be a simple request but I am going broke on coffee trying to find it. Ideas? Thanks -- Larry W8ER Ray, K9DUR wrote: Alan, If you read my reply to Chuck, AA5J, then you will see that the way the database software are structured, clicking on a frequency to add a custom label would not be an easy feature to implement. Each frequency does not exist in the database as an entity by itself, but rather the spectrum is broken down into frequency ranges that have a common label (80M CW, 40M SSB, etc.). In order to label a specific frequency, you have to replace 1 record in the database with 3. This can be done of course, but programmatically it is difficult somewhat dangerous to do as an automatic process. 73, Ray, K9DUR ___ FlexRadio Systems Mailing List FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archives: http://www.mail-archive.com/flexradio%40flex-radio.biz/ Knowledge Base: http://kb.flex-radio.com/ Homepage: http://www.flex-radio.com/ ___ FlexRadio Systems Mailing List FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archives: http://www.mail-archive.com/flexradio%40flex-radio.biz/ Knowledge Base: http://kb.flex-radio.com/ Homepage: http://www.flex-radio.com/ ___ FlexRadio Systems Mailing List FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archives: http://www.mail-archive.com/flexradio%40flex-radio.biz/ Knowledge Base: http://kb.flex-radio.com/ Homepage: http://www.flex-radio.com/
Re: [Flexradio] Editing the database wasn't what I wanted originally anyway
On 07/22/08 06:23 am I wrote: On 07/21/08 10:29 pm Ray, K9DUR wrote: Tim, You must be correct about Open Office causing a problem. Alan's statement that, ...the database is defined to permit only two decimal places... is absolutely not correct. The Low High fields in the BandText table are double-precision floating-point numbers, with at least 14 significant digits. With a maximum frequency of 65 MHz, this means that the values stored can have up to 12 digits after the decimal point. Typical values in these fields are entered to the nearest Hz, or 6 digits after the decimal point. Any limitation to only 2 digits must be either a limitation in or a setting of Open Office. Perhaps I jumped to the wrong conclusion based on what I observed: I could enter 14.236, but as soon as I moved over to the next field, what was displayed was 14.24. Note that what I had in mind when I posted my original feature request was the ability to click on a frequency and be offered the option to add my own label. I'm trying to gather a list of digital frequencies whose labels could be added in one fell swoop, but I still think some people might like a simple method of labeling some pet frequency as, for example, Old Farts' bitching net. Alan NV8A ___ FlexRadio Systems Mailing List FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archives: http://www.mail-archive.com/flexradio%40flex-radio.biz/ Knowledge Base: http://kb.flex-radio.com/ Homepage: http://www.flex-radio.com/
Re: [Flexradio] Editing the database wasn't what I wanted originally anyway
Yes, that would be a nice feature and if you haven't already done so, you need to add it as a feature request. But, with the current state of development as it is now with the emphasis on the new architecture, features of this nature are not going to be integrated into PowerSDR anytime in the near future, which is why I was providing an alternative method (work around) for your request. -Tim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alan NV8A Sent: Tuesday, July 22, 2008 10:19 AM To: Flex Group Subject: Re: [Flexradio] Editing the database wasn't what I wanted originally anyway On 07/22/08 06:23 am I wrote: On 07/21/08 10:29 pm Ray, K9DUR wrote: Tim, You must be correct about Open Office causing a problem. Alan's statement that, ...the database is defined to permit only two decimal places... is absolutely not correct. The Low High fields in the BandText table are double-precision floating-point numbers, with at least 14 significant digits. With a maximum frequency of 65 MHz, this means that the values stored can have up to 12 digits after the decimal point. Typical values in these fields are entered to the nearest Hz, or 6 digits after the decimal point. Any limitation to only 2 digits must be either a limitation in or a setting of Open Office. Perhaps I jumped to the wrong conclusion based on what I observed: I could enter 14.236, but as soon as I moved over to the next field, what was displayed was 14.24. Note that what I had in mind when I posted my original feature request was the ability to click on a frequency and be offered the option to add my own label. I'm trying to gather a list of digital frequencies whose labels could be added in one fell swoop, but I still think some people might like a simple method of labeling some pet frequency as, for example, Old Farts' bitching net. Alan NV8A ___ FlexRadio Systems Mailing List FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archives: http://www.mail-archive.com/flexradio%40flex-radio.biz/ Knowledge Base: http://kb.flex-radio.com/ Homepage: http://www.flex-radio.com/ ___ FlexRadio Systems Mailing List FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archives: http://www.mail-archive.com/flexradio%40flex-radio.biz/ Knowledge Base: http://kb.flex-radio.com/ Homepage: http://www.flex-radio.com/
