- HAM RADIO DELUXE 5 24 38 EXE 64 BIT
- HAM RADIO DELUXE 5 24 38 EXE UPDATE
- HAM RADIO DELUXE 5 24 38 EXE PC
- HAM RADIO DELUXE 5 24 38 EXE WINDOWS
HAM RADIO DELUXE 5 24 38 EXE PC
wav files saved, anything running on PC at the time, time of day - how random is random, daily, weekly - collecting info in a little text file may provide pointers you can report to the team that may help. > Collect info, what is happening around the time of the freeze, are. > I’m sure when it can be reproduced it will be fixed. I can see why no list is publicly available. All the dev team would end up doing is justifying the details. > As to a bug list - yes there are a couple of issues I would like to see fixed - I know if a list was published there would be a flurry of activity (myself included) ‘debating’ the severity/fix time scale - almost everyone would want their perceived bug higher up the list. > While it may appear dev team are doing nothing it could be they are waiting to see if some common factor pops up - 1 week, 1 month, 1 year … Your email seems to suggest you sort of expect the team to give it a higher priority (may be wrong but that was way I read the mail)
HAM RADIO DELUXE 5 24 38 EXE 64 BIT
> One option is to log the details, and then see how any others have issues over time, if more and more appear - is it same Rig? is it same version of the OS, is it the 32 or 64 bit version of the software (there are known issues with the 64 bit that are tied to some dev libs) - you never actually mentioned which version you were using - if 64 have you tried the 32 bit? how much time is justified in tracking it down - you said it is a small team.
HAM RADIO DELUXE 5 24 38 EXE WINDOWS
> From doing software development in a different life these are the worst sort of issues - it could be rig setup, it could be other applications on the PC, could be latest windows (or whatever) update, supplier codex, etc. > Just an observation - for many many people the software works well, the fact you cannot reproduce the issue does suggest IF it is an actual wsjtx bug it is pretty obscure. More people might be willing to get involved in fixing bugs if we could see the open issues. In your responses, you have given me some things to look for when the problem recurs. That’s why I offered to collect data to help isolate the problem. Having done engineering for more than 40 years, I know how difficult it can be to debug intermittent problems.
HAM RADIO DELUXE 5 24 38 EXE UPDATE
What happens to emailed bug reports? Can I search open issues to see if others have seen a similar issue and what additional information the developers would like? Can I update the bug when I have more information to add? How can I even know if the developer who knows that part of the system read the description of my issue? Are all open issues triaged periodically? Unless someone responds, it’s an information black hole which can be frustrating for people who report bugs. The documentation says to report bugs to the reflector. The issue I was trying to raise is one of process. WSJT-X is a great piece of software and I appreciate that it requires a lot of work, done by volunteers, to improve and maintain it.
I certainly do *not* expect my reported problem to be given priority treatment. > have fun! Operate as much of the 24-hour contest period at you want. Remember that the overarching objective is to > The contest itself starts at 12 UTC Saturday, 31 August and ends at 1159 > (Cabrillo log files) or (ADIF log file). > Tomorrow will host two more practices for the WW Digi Dx Contest: That's kind of challenge since we've started serving new modes FT4/FT8. We have prepared the scoreboard for the new WW Digi DX contest
0 kommentar(er)
