CHIRP

Where is you debug.log file? Does reverting back to the previous build 'fix' the issue?

Jim Unroe wrote in #note-1:

Where is you debug.log file? Does reverting back to the previous build 'fix' the issue?

I can not use the menus to get the debug.log file, I show a screenshot where clicking on "Help" just pops up with vertical white bar with none of the options present.

This is my first installation of chirp-next, I've only used legacy many years ago.

Michael Rogers wrote in #note-2:

Jim Unroe wrote in #note-1:

Where is you debug.log file? Does reverting back to the previous build 'fix' the issue?

I can not use the menus to get the debug.log file, I show a screenshot where clicking on "Help" just pops up with vertical white bar with none of the options present.

Following the steps below should put you in the folder where the debug.log is created.

1. Open CHIRP to create a new debug.log file
2. Close CHIRP to close the debug.log file
3. Type %appdata% in the Windows 11 search box and press Enter
4. In the Windows Explorer Roaming window that appears double-click the CHIRP folder
5. Attach the debug.log file to this issue

This is my first installation of chirp-next, I've only used legacy many years ago.

I just booted up a Windows 11 computer and upgraded CHIRP-next to the current build. No issues here. This issue appears to be limited to your install. The build has been available for at least 10 days and you are the first to report and issue.

Whenever I install an application in Windows 10/11 I always right-click the installer file and choose Run as administrator... even if the current user is an administrator. If trying this doesn't 'fix' it hopefully the debug.log file will give a clue with what the issue is.

Debug log looks fine to me. I've never seen anything like the screenshots you have, running Windows 10 and 11 here. Given that they're in the native system-drawn menus, I wouldn't even know where to start in debugging that. I feel pretty confident you're not the only person running a scaled DPI among the thousands of chirp users on windows. I run it in high DPI mode on macos, but of course they're system-drawn there as well so pretty much totally different. Tweaking my windows machine's display size a little locally doesn't seem to have any effect.

As Jim noted, perhaps going back a few months to an older build might be useful, just to confirm it's something systemic. I can't really think of anything chirp has done recently that would be relevant though.