Comments
-
Greg Hurrell
Yes, unless I'm not remembering things right, the "automatic" version check is not all that automatic right now. It was an oversight on my part that the last release went out with the "Check now" button hooked up, but the daily/weekly/monthly pop-up has no effect.
-
Greg Hurrell
I believe this is now fixed in the latest released version (0.4), with some caveats.
The automatic version checking code is now complete and in place. After releasing 0.4 I discovered a silly omission on my part that means that the automatic version check timer isn't started when you first launch the app, but only when you touch the automatic version checking preferences. I've already corrected this oversight in the current development build.
So it's now "working" in the current release (0.4), as long as you tickle the preferences after launching.
And it will work properly without the tickling in the next version (not yet sure whether I'll be numbering it 0.4.1 or 0.5; depends on the number of changes). I mean to release the next version fairly soon.
Unfortunately won't be able to mark this as confirmed fixed until the version *after* 0.4.1 or 0.5, because you'll need to install 0.4.1 or 0.5 first, and only when the *next* version comes out will be know for sure that the problem has been addressed.
In the meantime, adding the "fixed-in-prerelease" keyword.
-
Greg Hurrell
Changing assignment to reflect my new email address.
https://wincent.dev/a/news/archives/2006/05/change_of_email.php
-
Greg Hurrell
If you wish to confirm that this bug is fixed you can try out one of the Synergy Advance nightly builds. As noted in the nightlies page, these are automated builds which represent a snapshot of the current development status. They are not tested and may have issues of their own; the latest official release (0.4) is still the one that's recommended for daily use.
More information on nightlies here:
https://wincent.dev/s/nightlies/
A list of all Synergy Advance nightlies:
https://wincent.dev/a/about/wincent/weblog/nightlog/archives/synergy_advance/
Concretely, I believe this issues is fixed in revision 429 (link follows), or any later revision:
-
Greg Hurrell
Now that 0.5b is out removing "fixed-in-prerelease" keyword and marking as FIXED/CLOSED.
Add a comment
Comments are now closed for this issue.