This morning Don KB2YSI and I did some testing and confirmed this is the case with GridTracker v comparing his broken install and my working install. We found an upstream bug in NWJS where the Visual C Runtime was omitted from NWJS’s Windows dependency list. With thanks from all the fast reports of this issue, several members of the team spent most of the weekend testing and researching to figure out the WHY of why some Windows 10 PCs would load and launch GridTracker perfectly ok and others would load but not launch the GridTracker window. Matthew NR0Q Author NR0Q Posted on JanuJanuCategories GridTracker Fix for v Windows 10 The best part is that we’re going to make a lot of fun QSOs with everyone which to me is one of the best aspects of amateur radio! Afterwords we’ll collect all the log files and prepare a nice certificate to email out to anyone that worked us. So to celebrate as we’re testing all the new features and bug fixes we’re working on from February 1st through the 14th, members of the development and test teams will be signing with special event callsigns. What started as one hams way to not get buried in highlighters and printed off gridquare maps 4 years ago has evolved into the hamshack companion for operators of all kinds, we still track grids, but also now DXCCs, states, counties, CQ Zones, ITU Zones, WPX, various other awards, we have filtering and sorting that’ll make it much less intimidating for operating on today’s very crowded digital sub-bands. The plan is to release a version before Spring. We’ll continue to work on those with testing on some changes currently ongoing. And we’ve been working on old bugs and new features as well. It’s been a busy holiday season with the GridTracker team, a couple of us are settling into new jobs, one of us moved to a new state.
0 kommentar(er)
