Re: [wsjt-devel] Macro Expansion

2018-03-07 Thread Tom Melvin 
Hi Mike

Just throwing it out there - ‘FD’ while may be common on cw etc for some 
contests the CQ xx characters are generally taken as State / Providence / 
Region - while FD is not a US State - it could well apply to another country.  
Hardcoding it into one app does cause more confusion.  

The X? may work (Assuming no country) - but did I not see issues with a station 
XE  in recent fox/hound test - If some authority somewhere decides they will 
use XD as call there will be a mad rush to release patches assuming developers 
are around.

I would hate for some (no offence intended)  cock and bull method that  is not 
fully thought out - where would sota ref go, what about IOTA and all the other 
niche events. No doubt the one ‘’ macro that is not added/supported will be 
the one that causes most moans and complaints. 

Yes there should be a solution to that along with 6 character grids and a way 
of passing a ‘reference’ - SOTA ref/Contest Number/IOTA code - what it is I 
can’t help with but shoe horning a solution for xx% of users is not it.

Again no offence - just my personal view.

Regards

Tom
GM8MJV


On 7 Mar 2018, at 17:34, Black Michael via wsjt-devel 
 wrote:

> What other applications?  Is anybody interpreting the directed calls for any 
> purpose besides JTAlert giving it a "#" ??
> 
> To me it's a tradeoff between "confusion" where non-macro users would see the 
> 2-letter code and wonder what it's for and possibly ask questionsand the 
> ability to have "CQ FOX..." show up in Dxpedition mode and other such special 
> calls to let people know what's going on.
> 
> This has been asked numerous times for field day, SOTA, and such with no 
> other solution that I've seen.
> 
> 
> --- 
> Michael D. Black
> 
> 
> On Wednesday, March 7, 2018, 11:27:40 AM CST, Bill Somerville 
>  wrote:
> 
> 
> On 07/03/2018 17:19, Black Michael via wsjt-devel wrote:
> > Is there a downside to doing a macro expansion like this?
> >
> Hi Mike,
> 
> the obvious one is other applications not following suit. Changing the 
> interpretation of messages unilaterally is a recipe for confusion. At 
> least with the "E9aa" mapping to "CQ aa" the effect is relatively 
> transparent and if an application doesn't translate i.e. WSJT, then 
> users soon get the picture that E9EU means CQ EU and so on, whereas your 
> proposed mappings are rather more opaque.
> 
> 73
> Bill
> G4WJS.
> 
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> http://sdm.link/slashdot___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Macro Expansion

2018-03-07 Thread Black Michael via wsjt-devel 
What other applications?  Is anybody interpreting the directed calls for any 
purpose besides JTAlert giving it a "#" ??

To me it's a tradeoff between "confusion" where non-macro users would see the 
2-letter code and wonder what it's for and possibly ask questionsand the 
ability to have "CQ FOX..." show up in Dxpedition mode and other such special 
calls to let people know what's going on.
This has been asked numerous times for field day, SOTA, and such with no other 
solution that I've seen.

--- 
Michael D. Black 

On Wednesday, March 7, 2018, 11:27:40 AM CST, Bill Somerville 
 wrote:  
 
 On 07/03/2018 17:19, Black Michael via wsjt-devel wrote:
> Is there a downside to doing a macro expansion like this?
>
Hi Mike,

the obvious one is other applications not following suit. Changing the 
interpretation of messages unilaterally is a recipe for confusion. At 
least with the "E9aa" mapping to "CQ aa" the effect is relatively 
transparent and if an application doesn't translate i.e. WSJT, then 
users soon get the picture that E9EU means CQ EU and so on, whereas your 
proposed mappings are rather more opaque.

73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Macro Expansion

2018-03-07 Thread Bill Somerville 

On 07/03/2018 17:19, Black Michael via wsjt-devel wrote:

Is there a downside to doing a macro expansion like this?


Hi Mike,

the obvious one is other applications not following suit. Changing the 
interpretation of messages unilaterally is a recipe for confusion. At 
least with the "E9aa" mapping to "CQ aa" the effect is relatively 
transparent and if an application doesn't translate i.e. WSJT, then 
users soon get the picture that E9EU means CQ EU and so on, whereas your 
proposed mappings are rather more opaque.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Macro Expansion

2018-03-07 Thread Black Michael via wsjt-devel 
Is there a downside to doing a macro expansion like this?
I've got this working and it only affects the display and not what's 
transmitted.  Takes advantage of unused country codes which I suppose someday 
might be used..though X countries are fairly rare and calling for them even 
more rare.  Q would be another choice but X sounds like "Xpansion" so is a 
touch more intuitive.  On the other hand QA is the only Q country code and 
probably less chance of collision.

CQ XH K1JT FN20  CQ FOX K1JT FN20CQ XG K1JT +05 >> CQ SPLIT K1JT +5KHZCQ XG 
K1JT -01 >> CQ SPLIT K1JT -1KHZ

+void MainWindow::macroExpansion(QString& msg)
+{
+  // Let's avoid certain country codes for now
+  // See https://www.ng3k.com/Dxcc/dxcc.html
+  // These are good for now
+  // XA XB XC XD XG XH XI XJ XK XL XM XN XO XP XQ XR XS
+  msg.replace(" FD "," FIELDDAY ");
+  msg.replace(" XA "," TEST ");
+  msg.replace(" XB "," BEACON ");
+  msg.replace(" XC "," CONTEST ");
+  msg.replace(" XD "," DXPEDITION ");
+  if (msg.contains(" XG ")) {
+    msg.replace(" XG "," SPLIT ");
+    QString khz = msg.mid(0,msg.length()-1);
+    if (msg.mid(msg.length()-3)=="-") {
+    khz = "-" + khz;
+    }
+    else {
+    khz = "+" + khz;
+    }
+    msg.chop(3);
+    msg += khz + "KHZ";
+  }+  msg.replace(" XH "," FOX ");
+  msg.replace(" XM "," EMAILME ");
+  msg.replace(" XO "," 1010 ");
+  msg.replace(" XP "," QSOPARTY ");
+  msg.replace(" XS "," SOTA ");
+}


de Mike W9MDB
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel