Comments
-
Greg Hurrell
Ok, I believe this is now fixed for the next public preview release (0.3). I can no longer see the tearing or artefacts, with or without Quartz Debug, although BBEdit continues to be slow as a dog at scrolling (independently of whether Synergy Advance is running or not).
Adding fixed-in-prerelease keyword.
-
Greg Hurrell
- ** Bug 284 has been marked as a duplicate of this bug. ***
-
Jason Snell
I am using the development version and not seeing this bug at present, but it's somewhat intermittent, so I'll report back again one way or another.
-
Jason Snell
The development version you sent does seem to fix this problem.
-
Greg Hurrell
(In reply to comment #4)
The development version you sent does seem to fix this problem.
Good to hear.
-
Greg Hurrell
- ** Bug 317 has been marked as a duplicate of this bug. ***
-
Greg Hurrell
- ** Bug 319 has been marked as a duplicate of this bug. ***
-
Greg Hurrell
I am getting a few duplicate reports for this issue. For the record, you can download a build with the fix.
SHA1 checksum: 888e30fb6b38dd57d2dfbe1fbef0854a7cd53901
By the way, as far as I can tell this is not actually a Synergy Advance bug. The program actually is issuing a window close instruction to Cocoa, but for some reason Cocoa is not ordering the window out of the screen, resulting in the glitches.
-
Greg Hurrell
- ** Bug 336 has been marked as a duplicate of this bug. ***
-
Greg Hurrell
This fix is now available in the just-released version 0.4b. For more information:
https://wincent.dev/a/news/archives/2006/03/synergy_advance_4.php
Marking as FIXED/CLOSED.
Add a comment
Comments are now closed for this issue.