When entering Trx Pwr using my numberic island the dot is not converted to a comma. (Might be considered even as feature instead as bug)
Maybe you should alter the keycode for 1000-seperator to the keycode for decimal separator in the key-up event or make this a overridable setting for those using thousandsseperators for kilo/MegaWatts.
Now for the bug I could call bug instead of feature :
When setting filters for QSO's to display with Trx Power Dec I notice the following :
Trx Power Dec <= 5.000 gives me all QSO's from 0 to 100 W
Trx Power Dec < 5.000 gives me all QSO's from 0 to 100 W
Trx Power Dec <= 5 gives me all QSO's from 0 to 5 W
Trx Power Dec < 5 gives me all QSO's from 0 to 4.999 W
Trx Power Dec = 5.000 gives me no QSO's
Trx Power Dec = 5 gives me all QSO's with 5 W
I did not try out other combinations but I think you know where to look.
TrxPower Dec in 1.17
TrxPower Dec in 1.17
PB4FUN Meindert; Rig : Icom IC-9100 / Ant: Falcon OUT-250-B @4m AGL; 144 MHz 16 el @ 4m AGL; 70 cm 23 el @ 5 m AGL
- IW3HMH
- Site Admin
- Posts: 2926
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: TrxPower Dec in 1.17
Usually in search fields you must NOT use thousand separators.
Those searches will be made directly on the database, that doesn't have thousand separators on it.
I'm already working with user language localization to change values to the recognized decimal separator, but in search you should avoid thousand separators.
This is a "drawback" from search, that is flexible to allow you make everything on your queries but must comply to some rules.
Those searches will be made directly on the database, that doesn't have thousand separators on it.
I'm already working with user language localization to change values to the recognized decimal separator, but in search you should avoid thousand separators.
This is a "drawback" from search, that is flexible to allow you make everything on your queries but must comply to some rules.
Daniele Pistollato - IW3HMH
Re: TrxPower Dec in 1.17
You mean something like this ?
How about an expert mode for the search using real SQL ?
Code: Select all
private void numericUpDown1_KeyPress(object sender, KeyPressEventArgs e)
{
if (e.KeyChar == '.' || e.KeyChar == ',')
{
e.KeyChar = System.Globalization.NumberFormatInfo.CurrentInfo.NumberDecimalSeparator.ToString()[0];
}
}
PB4FUN Meindert; Rig : Icom IC-9100 / Ant: Falcon OUT-250-B @4m AGL; 144 MHz 16 el @ 4m AGL; 70 cm 23 el @ 5 m AGL
Re: TrxPower Dec in 1.17
Found another one concerning TrxPowerDecimal
Step 1 : Export to Adif (tried 2.0 version)
Step 2 : Import on another PC having an empty log
A QSO with 0.150 W has now 15.000 W
<TX_PWR:4>0,15 <COMMENT:6>0.15 W
Shouldn't the Adif be with dot as decimal separator so its an error in generating Adif ?
Step 1 : Export to Adif (tried 2.0 version)
Step 2 : Import on another PC having an empty log
A QSO with 0.150 W has now 15.000 W
<TX_PWR:4>0,15 <COMMENT:6>0.15 W
Shouldn't the Adif be with dot as decimal separator so its an error in generating Adif ?
PB4FUN Meindert; Rig : Icom IC-9100 / Ant: Falcon OUT-250-B @4m AGL; 144 MHz 16 el @ 4m AGL; 70 cm 23 el @ 5 m AGL
- IW3HMH
- Site Admin
- Posts: 2926
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: TrxPower Dec in 1.17
Yes, i will check for that and release probably an update.
Thanks for reporting
Thanks for reporting
Daniele Pistollato - IW3HMH