nanovna-saver
nanovna-saver copied to clipboard
Erratic display behaviour with "Hide Data" in Markers and maximized
When clicking on "Hide Data" in Markers section the parts of displayed information start to twitch erratically (many times per second) when main app window maximized full screen - the graphs (ie 3 selected) several pixels left-right direction and the "Reference sweep" part on the left several pixels up/down direction. No erratic twitching when the marker data are shown. No erratic twitching when main app window made smaller than maximized. It does jerk with or without nanovna-h4 connected. Nanovna-Saver 0.3.4 Win 10 64bits, 1920x1080 pixels display
The picture jerks when - ie.:
a) the main app window is maximized, and
b) there are 3 graphs selected, and
c) one of them is Polar Plot or Smith Chart.
I can not duplicate this
From: IMO [email protected] Sent: 10 July 2020 12h43 To: NanoVNA-Saver/nanovna-saver [email protected] Cc: Subscribed [email protected] Subject: Re: [NanoVNA-Saver/nanovna-saver] Erratic display behaviour with "Hide Data" in Markers and maximized (#233)
The picture jerks when ie.: a) the main app window is maximized a) there are 3 graphs selected b) one of them is Polar Plot or Smith Chart https://user-images.githubusercontent.com/7240123/87146164-d0b56880-c2aa-11ea-908a-5a7fa4e2a7a2.PNG
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/NanoVNA-Saver/nanovna-saver/issues/233#issuecomment-656610653 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABP3LR6IDAMIL77XQJYEME3R23WD5ANCNFSM4OVQVKFA . https://github.com/notifications/beacon/ABP3LR65DBLVEMNX4BF7OB3R23WD5A5CNFSM4OVQVKFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE4RRKXI.gif
Here an example of jerking in .avi screen capture.. Erratic display.zip
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍 Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions!