DipTrace 5.2 release

[Serg]

Cross selection is disabled. Never used that. The Schematic tool was never open when it happened anyway. I'm in "Default Mode" when it happens. As I said, I think it has to to with automatic highlighting of nets/components when moving the mouse over them.
I haven't found an option to disable this auto highlighting.
Side note: I just noticed that just clicking the left mouse button anywhere also fixes the problem (until it happens again). Right clicking doesn't help though. Just brings up the context menu.
I added an MP4 which shows the problem. I use left click several times to recover from the issue, then resize the screen and cause the issue. Then the issue won't usually happen until I rescale again.

This may be related to a conflict in the video card operation. Try changing the graphics mode from the main menu: View → Graphics Mode. What are your operating system and monitor parameters?

[novarm44]

Cross selection is disabled. Never used that. The Schematic tool was never open when it happened anyway. I'm in "Default Mode" when it happens. As I said, I think it has to to with automatic highlighting of nets/components when moving the mouse over them.
I haven't found an option to disable this auto highlighting.
Side note: I just noticed that just clicking the left mouse button anywhere also fixes the problem (until it happens again). Right clicking doesn't help though. Just brings up the context menu.
I added an MP4 which shows the problem. I use left click several times to recover from the issue, then resize the screen and cause the issue. Then the issue won't usually happen until I rescale again.

Thank You for the video. I have a few ideas how it may happen and will try to fix. Generally it looks strange on your screen, normally graphics should works smoother.

[0xdeadbeef]

@Serg:
As stated before, it happens with Direct3D and OpenGL, it doesn't happen with a still installed v4 and I'm pretty sure it didn't happen with 5.1.
OS is Win10, CPU is a Core i7 6700K, GPU is an RTX2080. Not sure what you mean with "monitor parameters". Anyway, it's somewhat impossible that the monitor could have anything do to with that.
After the issue first occurred, I installed at least two Nvidia graphic driver updates but the behavior didn't change to the better or worse.

@novarm44:
I had switched to Direct3D when recording this, which is a bit slower than OpenGL on my PC, but the video recording doesn't represent what I saw in real life even though I used 60Hz for the recording.
Especially the flickering while scaling the window exists only in the recording but not in real life. I assume it has something to do with recording only the application window (grabbing some internal buffer updated faster than 60Hz or something like this).
But I figured it would be better to have a small video of only the windows instead of trying to record a full screen and wasting an hour to post-process and compress it.
The issue itself is very clearly visible.

[novarm44]

@novarm44:
I had switched to Direct3D when recording this, which is a bit slower than OpenGL on my PC, but the video recording doesn't represent what I saw in real life even though I used 60Hz for the recording.
Especially the flickering while scaling the window exists only in the recording but not in real life. I assume it has something to do with recording only the application window (grabbing some internal buffer updated faster than 60Hz or something like this).
But I figured it would be better to have a small video of only the windows instead of trying to record a full screen and wasting an hour to post-process and compress it.
The issue itself is very clearly visible.

The problem is we can not reproduce it anywhere. Also our development/test PCs are much slower. My regular working machine is mini PC with i7-1060NG7 and integrated graphics - this is made specially to see necks in the software while development/tests (+ I like full silence of 10W processor machine ).
I've investigated the code, corrected a few things and have found one possible place which may produce such effect if graphics data are provided incorrectly to it.

update: Finally, I was able to reproduce it!!! Will try to find the reason and fix.

update 2: Fixed, updated pcb.exe is attached (please place it to C:\Program files\DipTrace) - please try to work with it on your machine

[0xdeadbeef]

Great, thanks a lot! With this "Pcb_screen_debug.exe", I can't reproduce the issue anymore while it happens immediately again when I switch back to the original "pcb.exe".
I'm very happy that you took this report seriously even though you could not easily reproduce it and that you found a fix in such a short time.

This being said, since I wanted to work on a PCB this weekend: I noticed that the debug version is 10MB smaller, so is there anything missing or another reason I should not use it and wait for the official 5.2.0.3 instead?
Or is it OK to use this version while waiting for an official update?

[novarm44]

Great, thanks a lot! With this "Pcb_screen_debug.exe", I can't reproduce the issue anymore while it happens immediately again when I switch back to the original "pcb.exe".
I'm very happy that you took this report seriously even though you could not easily reproduce it and that you found a fix in such a short time.

This being said, since I wanted to work on a PCB this weekend: I noticed that the debug version is 10MB smaller, so is there anything missing or another reason I should not use it and wait for the official 5.2.0.3 instead?
Or is it OK to use this version while waiting for an official update?

It was reproduced on one of our files, in one of inner layers for net highlighting when you do window resize like in your video. Other layers of this file worked properly, other files too. Fixing is not hard if you can reproduce it, but almost impossible if can't.

This is 32 bit version (it is easier to compile/debug it, so we use it for development). Autorouter and STEP import export will not work because they are 64-bit dlls in your version, however there is no difference in other features unless you are doing very big projects, which may require more memory and performance.

[0xdeadbeef]

OK, great, thanks. I never really use the autorouter anyway and don't think I will need to import STEP files for this project, so this makes waiting for a new version much more comfortable for me

[Flux]

Diptrace:

Will there be a update official soon for the bug fix?

[0xdeadbeef]

Does this mean you have the same issue?

[novarm44]

Diptrace:

Will there be a update official soon for the bug fix?

Yes, next week.