Date   
Re: flmsg alpha 4.0.8.02

Mike P.
 

Roger.

--- Mike, AE7XB

On 1 Jan 2019 at 22:03, Dave wrote:

flmsg hands off the entire data stream to fldigi.  Abort the
transmission using the fldigi T/R button.

Dave

On 1/1/19 7:24 PM, Mike P. wrote:
Dave, good compile on flmsg-4.0.8.02 alpha.

A double-click on the autosend only giveS one instance
of a message transmission, as it should.

However, deliberately clicking on the autosend stacks
up multiple instances of the message in the transmit
buffer. I believe that once the autosend has buffered
the message for transmission, the autosend button
should change into an "Abort" button, in which the user
can cleanly cancel his transmission.

Flamp has a very nice abort function; an option which
would greatly benefit flmsg.

73

--- Mike, AE7XB

Electronics usually don't work after the magic smoke is released.

Re: flmsg alpha 4.0.8.02

Dave
 

flmsg hands off the entire data stream to fldigi.  Abort the transmission using the fldigi T/R button.

Dave

On 1/1/19 7:24 PM, Mike P. wrote:
Dave, good compile on flmsg-4.0.8.02 alpha.

A double-click on the autosend only giveS one instance
of a message transmission, as it should.

However, deliberately clicking on the autosend stacks
up multiple instances of the message in the transmit
buffer. I believe that once the autosend has buffered
the message for transmission, the autosend button
should change into an "Abort" button, in which the user
can cleanly cancel his transmission.

Flamp has a very nice abort function; an option which
would greatly benefit flmsg.

73

--- Mike, AE7XB

On 1 Jan 2019 at 18:59, Dave wrote:

* flmsg-4.0.8.02.tar.gz
* flmsg-4.0.8.02_setup.exe
Resolves build issue on Mint 19 / 64 bit.� Corrects warnings for all builds.
73, David, W1HKJ
Electronics usually don't work after the magic smoke is released.




Re: flmsg alpha 4.0.8.02

Mike P.
 

Dave, good compile on flmsg-4.0.8.02 alpha.

A double-click on the autosend only giveS one instance
of a message transmission, as it should.

However, deliberately clicking on the autosend stacks
up multiple instances of the message in the transmit
buffer. I believe that once the autosend has buffered
the message for transmission, the autosend button
should change into an "Abort" button, in which the user
can cleanly cancel his transmission.

Flamp has a very nice abort function; an option which
would greatly benefit flmsg.

73

--- Mike, AE7XB

On 1 Jan 2019 at 18:59, Dave wrote:


* flmsg-4.0.8.02.tar.gz
* flmsg-4.0.8.02_setup.exe
Resolves build issue on Mint 19 / 64 bit.  Corrects warnings for all builds.
73, David, W1HKJ
Electronics usually don't work after the magic smoke is released.

Re: flmsg alpha 4.0.8.02

Ron
 

Dave,

That did it.  You must have been coding during the bowl football games today :-)

Thanks and 73, Ron NY3J

On 1/1/19 7:59 PM, Dave wrote:

Resolves build issue on Mint 19 / 64 bit.  Corrects warnings for all builds.

73, David, W1HKJ



flmsg alpha 4.0.8.02

Dave
 

Resolves build issue on Mint 19 / 64 bit.  Corrects warnings for all builds.

73, David, W1HKJ


Re: Uncommanded repeat of FLMsg

Mike P.
 

Dave, on Linux Mint 19, I also get strcasecmp
declaration compile error on flmsg-4.0.8.01 alpha.

--- Mike, AE7XB

On 1 Jan 2019 at 8:18, Dave wrote:

Thanks Ron.  My Mint 19.0 test build also shows a strcasecmp declaration error

Dave
Electronics usually don't work after the magic smoke is released.

Re: Uncommanded repeat of FLMsg

Dave
 

Thanks Ron.  My Mint 19.0 test build also shows a strcasecmp declaration error

Dave

On 1/1/19 7:27 AM, Ron wrote:
Sorry, I meant Linux Mint 19.0.

Ron NY3J

On 1/1/19 8:23 AM, Ron wrote:
Hi Dave,

It worked like a charm on my Windows 10 machine.  Double clicking within two seconds ignores the 2nd click.  After 2 seconds it will send it twice.

On my Linux Mint 18.0 machine the make command failed.  I sent the log to your private email.

Thanks, 73, Ron NY3J

On 1/1/19 7:53 AM, Dave wrote:
Please test

Includes this source code change

commit 3355087d05c2db0e0087de68137b398ba09bb740
Author: David Freese <w1hkj@...>
Date:   Tue Jan 1 06:21:54 2019 -0600

    Double click
   
      * add double click timer to AutoSend button
        - ignore multiple clicks of button that occur
          within a 2 second window.

73 & HNY, David, W1HKJ

On 12/31/18 2:13 PM, Ron wrote:
Hi Bart and Dave,

Excuse me for busting in like this.  I've had this happen to me with my impatience or just a nervous double click and I see it often with other people on the nets.  It gets worse when you try to interrupt the second transmission and it stays queued and if you send something else the Flmsg will continue.  I just tried it again and noticed that if you double click the autosend you are prompted to save the message.  Then it only gets sent once.  If you save it first then double, triple click autosend it will send that many times.

73, Ron NY3J

On 12/31/18 2:37 PM, Dave wrote:
I can force as many as 5 repeats by multiple mouse clicks on the AutoSend button.  There may be a bit of operator impatience at play here.  There is a finite, variable amount of time between the AutoSend closure and the onset of fldigi transmission.  The operator may think that the button closure did not occur and press AutoSend a second time.  It might help if I provided a visual confirmation that the data transfer to fldigi took place.  Perhaps a pop up confirmation dialog that the operator needed to acknowledge before any other AutoSend events are allowed.

Dave

On 12/31/18 1:26 PM, bartpearl via Groups.Io wrote:
Dave:

Both are using Windows, I think Windows 10 but I'm not sure.  It's VHF through repeaters.  Don't know about the mouse and buttons, I was going to ask on the next net (Wednesday night). 

It happened with two operators.  One is very proficient, and it only happened to him once.  The other is very new to NBEMS but seems to be catching on pretty quick.  It's happened several times with him.

I was planning on asking him to slow down the double-click speed setting and see if that stopped it. 

Bart N5BLP






Re: Uncommanded repeat of FLMsg

Ron
 

Sorry, I meant Linux Mint 19.0.

Ron NY3J

On 1/1/19 8:23 AM, Ron wrote:
Hi Dave,

It worked like a charm on my Windows 10 machine.  Double clicking within two seconds ignores the 2nd click.  After 2 seconds it will send it twice.

On my Linux Mint 18.0 machine the make command failed.  I sent the log to your private email.

Thanks, 73, Ron NY3J

On 1/1/19 7:53 AM, Dave wrote:
Please test

Includes this source code change

commit 3355087d05c2db0e0087de68137b398ba09bb740
Author: David Freese <w1hkj@...>
Date:   Tue Jan 1 06:21:54 2019 -0600

    Double click
   
      * add double click timer to AutoSend button
        - ignore multiple clicks of button that occur
          within a 2 second window.

73 & HNY, David, W1HKJ

On 12/31/18 2:13 PM, Ron wrote:
Hi Bart and Dave,

Excuse me for busting in like this.  I've had this happen to me with my impatience or just a nervous double click and I see it often with other people on the nets.  It gets worse when you try to interrupt the second transmission and it stays queued and if you send something else the Flmsg will continue.  I just tried it again and noticed that if you double click the autosend you are prompted to save the message.  Then it only gets sent once.  If you save it first then double, triple click autosend it will send that many times.

73, Ron NY3J

On 12/31/18 2:37 PM, Dave wrote:
I can force as many as 5 repeats by multiple mouse clicks on the AutoSend button.  There may be a bit of operator impatience at play here.  There is a finite, variable amount of time between the AutoSend closure and the onset of fldigi transmission.  The operator may think that the button closure did not occur and press AutoSend a second time.  It might help if I provided a visual confirmation that the data transfer to fldigi took place.  Perhaps a pop up confirmation dialog that the operator needed to acknowledge before any other AutoSend events are allowed.

Dave

On 12/31/18 1:26 PM, bartpearl via Groups.Io wrote:
Dave:

Both are using Windows, I think Windows 10 but I'm not sure.  It's VHF through repeaters.  Don't know about the mouse and buttons, I was going to ask on the next net (Wednesday night). 

It happened with two operators.  One is very proficient, and it only happened to him once.  The other is very new to NBEMS but seems to be catching on pretty quick.  It's happened several times with him.

I was planning on asking him to slow down the double-click speed setting and see if that stopped it. 

Bart N5BLP





Re: Uncommanded repeat of FLMsg

Ron
 

Hi Dave,

It worked like a charm on my Windows 10 machine.  Double clicking within two seconds ignores the 2nd click.  After 2 seconds it will send it twice.

On my Linux Mint 18.0 machine the make command failed.  I sent the log to your private email.

Thanks, 73, Ron NY3J

On 1/1/19 7:53 AM, Dave wrote:
Please test

Includes this source code change

commit 3355087d05c2db0e0087de68137b398ba09bb740
Author: David Freese <w1hkj@...>
Date:   Tue Jan 1 06:21:54 2019 -0600

    Double click
   
      * add double click timer to AutoSend button
        - ignore multiple clicks of button that occur
          within a 2 second window.

73 & HNY, David, W1HKJ

On 12/31/18 2:13 PM, Ron wrote:
Hi Bart and Dave,

Excuse me for busting in like this.  I've had this happen to me with my impatience or just a nervous double click and I see it often with other people on the nets.  It gets worse when you try to interrupt the second transmission and it stays queued and if you send something else the Flmsg will continue.  I just tried it again and noticed that if you double click the autosend you are prompted to save the message.  Then it only gets sent once.  If you save it first then double, triple click autosend it will send that many times.

73, Ron NY3J

On 12/31/18 2:37 PM, Dave wrote:
I can force as many as 5 repeats by multiple mouse clicks on the AutoSend button.  There may be a bit of operator impatience at play here.  There is a finite, variable amount of time between the AutoSend closure and the onset of fldigi transmission.  The operator may think that the button closure did not occur and press AutoSend a second time.  It might help if I provided a visual confirmation that the data transfer to fldigi took place.  Perhaps a pop up confirmation dialog that the operator needed to acknowledge before any other AutoSend events are allowed.

Dave

On 12/31/18 1:26 PM, bartpearl via Groups.Io wrote:
Dave:

Both are using Windows, I think Windows 10 but I'm not sure.  It's VHF through repeaters.  Don't know about the mouse and buttons, I was going to ask on the next net (Wednesday night). 

It happened with two operators.  One is very proficient, and it only happened to him once.  The other is very new to NBEMS but seems to be catching on pretty quick.  It's happened several times with him.

I was planning on asking him to slow down the double-click speed setting and see if that stopped it. 

Bart N5BLP




Uncommanded repeat of FLMsg

Dave
 

Please test

Includes this source code change

commit 3355087d05c2db0e0087de68137b398ba09bb740
Author: David Freese <w1hkj@...>
Date:   Tue Jan 1 06:21:54 2019 -0600

    Double click
   
      * add double click timer to AutoSend button
        - ignore multiple clicks of button that occur
          within a 2 second window.

73 & HNY, David, W1HKJ

On 12/31/18 2:13 PM, Ron wrote:
Hi Bart and Dave,

Excuse me for busting in like this.  I've had this happen to me with my impatience or just a nervous double click and I see it often with other people on the nets.  It gets worse when you try to interrupt the second transmission and it stays queued and if you send something else the Flmsg will continue.  I just tried it again and noticed that if you double click the autosend you are prompted to save the message.  Then it only gets sent once.  If you save it first then double, triple click autosend it will send that many times.

73, Ron NY3J

On 12/31/18 2:37 PM, Dave wrote:
I can force as many as 5 repeats by multiple mouse clicks on the AutoSend button.  There may be a bit of operator impatience at play here.  There is a finite, variable amount of time between the AutoSend closure and the onset of fldigi transmission.  The operator may think that the button closure did not occur and press AutoSend a second time.  It might help if I provided a visual confirmation that the data transfer to fldigi took place.  Perhaps a pop up confirmation dialog that the operator needed to acknowledge before any other AutoSend events are allowed.

Dave

On 12/31/18 1:26 PM, bartpearl via Groups.Io wrote:
Dave:

Both are using Windows, I think Windows 10 but I'm not sure.  It's VHF through repeaters.  Don't know about the mouse and buttons, I was going to ask on the next net (Wednesday night). 

It happened with two operators.  One is very proficient, and it only happened to him once.  The other is very new to NBEMS but seems to be catching on pretty quick.  It's happened several times with him.

I was planning on asking him to slow down the double-click speed setting and see if that stopped it. 

Bart N5BLP



Shortwave Radiogram, 14-16 December 2018

kd9xb
 

Shortwave Radiogram -- digital modes via shortwave broadcast -- this weekend is in MFSK32 and MFSK64 ...

http://swradiogram.net/post/181110910437/shortwave-radiogram-14-16-december-2018

Kim
KD9XB

Re: New FLRig

Dave
 

By "launcher", I am referring to the application icon which is usually installed to the /Applications folder.

Just trying to understand why I do not see the same behavior on my 10.14 installation.

Dave

On 12/7/18 8:28 AM, Keith Kaiser wrote:
  • Are you installing the launcher to /Applications or some other location?  I’m not sure what the launcher is, probably something I should know or do know by a different name.

  • Are you launching with a left click on the launcher, or using a right click / menu pick?  Again, what is the “launcher”?

  • Are you launching with a left click on a dock icon? I am. I generally keep my Ham related apps in the Doc and use left click to select it.

  • Are you launching from a terminal window using something similar to "open /Applications/flrig-1.3.42.01.app” I’m fairly noble with the terminal as I do a lot of Raspberry Pi work, however I’ve not used it to launch any of the FL apps, including FLRig.

Keith, WA0̷TJT

Re: New FLRig

Keith Kaiser
 

  • Are you installing the launcher to /Applications or some other location?  I’m not sure what the launcher is, probably something I should know or do know by a different name.

  • Are you launching with a left click on the launcher, or using a right click / menu pick?  Again, what is the “launcher”?

  • Are you launching with a left click on a dock icon? I am. I generally keep my Ham related apps in the Doc and use left click to select it.

  • Are you launching from a terminal window using something similar to "open /Applications/flrig-1.3.42.01.app” I’m fairly noble with the terminal as I do a lot of Raspberry Pi work, however I’ve not used it to launch any of the FL apps, including FLRig.

Keith, WA0̷TJT



Re: New FLRig

Dave
 

Thanks Keith.  macOS Mojave exhibits some strange behavior.  I was not able to replicate the -psn_xxxx command line parameter on my minMac running 10.14, either with the posted dmg (built on 10.13) or with a binary built on 10.14. 
  • Are you installing the launcher to /Applications or some other location?
  • Are you launching with a left click on the launcher, or using a right click / menu pick?
  • Are you launching with a left click on a dock icon?
  • Are you launching from a terminal window using something similar to "open /Applications/flrig-1.3.42.01.app"
73, David, W1HKJ

On 12/6/18 9:17 AM, Keith Kaiser wrote:
The alpha version 1.3.42.01 came right up without any issues.

Re: New FLRig

Keith Kaiser
 

The alpha version 1.3.42.01 came right up without any issues.

Re: New FLRig

Dave
 

Please test the alpha version dmg found at http://www.w1hkj.com/alpha/flrig.

It is specifically compiled for OS-X 10.13 and later and should correct for this startup issue (caused by changes in the way the OS launches the application).



David

Flmsg shows up as Fllog on launcher in Ubuntu 18.04

W. T. Jones <wn3lif@...>
 

Minor issue but I thought I'd mention it.

OS - Ubuntu 18.04

When Flmsg is running and an Alt Tab is pressed to move to the next program Flmsg shows up as Fllog with no icon.

On the launcher it is the same. See attached screen shot. I could not capture the Alt Tab banner.

Again, not a big deal. Just I thought I'd mention it.

Screenshot from 2018-12-05 16-52-51.png
Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

Re: New FLRig

Dave
 

What version on the OS

On 12/5/18 10:37 AM, Keith Kaiser wrote:

Keith, WA0̷TJT


I installed the new FLRig on my MacBook Pro but in trying to launch I get this. Resetting and trying all the usual things I still get this.

Thoughts

Keith, WA0̷TJT



New FLRig

Keith Kaiser
 


Keith, WA0̷TJT


I installed the new FLRig on my MacBook Pro but in trying to launch I get this. Resetting and trying all the usual things I still get this.

Thoughts

Keith, WA0̷TJT


flrig 1.3.41 posted

Dave
 

At Source Forge and at the w1hkj.com web site:

Read the readme.txt for information on changes since 1.3.40.

1.3.41 supersedes all prior alpha releases in the 1.3.41.xx series.

73, David, W1HKJ