You can submit a git diff would be the easiest.
Mike W9MDB

 

    On Wednesday, November 20, 2024 at 05:34:22 PM CST, mark--- via wsjt-devel 
<wsjt-devel@lists.sourceforge.net> wrote:  
 
 
Not quite what I was thinking, although that’s a possibility.

  

The current “Error in Sound Input” dialog has only an OK button.  If you hit 
that OK button and the sound card still isn’t there, the same dialog comes 
right back.

  

I was thinking about just always trying to reconnect when the user hits “OK”.  

  

I actually have not walked through this in about a month (it just keeps nagging 
me) so I need to walk through the code again before I really decide.  At work 
we have UX interface folks who decide all that and we just make it look like 
they say to.  If the OK option just goes back and does nothing (which I think 
is what it is doing now), there is no reason not to at least try to reconnect.

  

I admit that I am on a single configuration train of thought her, and not 
considering cases where the soundcard is in the computer or where it is 
external in a USB dongle where the power is supplied by the USB.  I will look 
at those cases before I push a patch.

  

Right now, I just wanted to make sure that I knew the ground rules.  Are 
changes normally delivered as patches (i.e., input to a linux patch command), 
or do people generally make git branches and push the branch and ask that it be 
delivered to master?  Is there a document?

  

Thanks

Mark

  

From: Black Michael <mdblac...@yahoo.com> 
Sent: Wednesday, November 20, 2024 5:19 PM
To: wsjt-devel@lists.sourceforge.net
Cc: m...@sladenfamily.com
Subject: Re: [wsjt-devel] Question about requesting changes

  

I'm sure such a patch would be accepted.

  

Are you talking about making the popup dialog have a "Retry" button?

  

Mike W9MDB

  

  

  

  

On Wednesday, November 20, 2024 at 03:53:05 PM CST, mark--- via wsjt-devel 
<wsjt-devel@lists.sourceforge.net> wrote: 

  

  

Hello,

 

I have been a happy user of wsjt-x for years, but recently I noticed an issue 
that I would like to fix.

 

I am using a QRPLabs QMX+ transceiver mostly right now.  It is a great little 
rig.  An old version of this rig was reviewed in last month’s QST.  It is 
gaining a lot of popularity because it is inexpensive and a great little 
transceiver.  

 

My problem with the QMX+ is that it has an USB sound card internal to the 
transceiver.  I am in the habit of turning off the transceiver, unplugging the 
antenna, but leaving the computer running when I am done for the night or if a 
thunderstorm comes my way.  That means the soundcard interfaces go away, and I 
get a warning message and have to return to Settings/Audio and click the Input 
and Output before I can start to play.  

 

Not a huge problem, but annoying enough that I would like to fix it, both for 
myself and for the other QMX/QMX+/QDX users.

 

I have looked into the problem, and I have identified what needs to be done.  I 
have been coding since I learned Fortran in junior high school in the ‘70’s, so 
I know my way around.  I am moving to a Raspberry Pi for portable work, and 
since it is easy enough to build from source, I figured I would do that, and 
then poke the fixes in until it works.  

 

My question is, if I get something I like, is there a pathway to making a merge 
request and adoption in the master branch?

 

Thanks

Mark/W8GU

_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to