Thank you!
1 Like
2.41.5 (5) is the current production app and the version I stated has the issue. I was trying to ascertain if the problem has been fixed in the beta release candidate before it goes public.
K6CCC stated that it’s working correctly in release candidate version 2.42.0 (20), so I’m assuming the issue has been resolved (in beta).
2 Likes
No problem… thank you for the help!
2 Likes
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.