http://fiji.sc/bugzilla/show_bug.cgi?id=585
--- Comment #3 from Johannes Schindelin <[email protected]> --- Hi Carol, it is good that you specified exactly the steps you performed because that was not clear from the original bug report. Based on the original account, I had chased around for 30 minutes before I gave up and admitted to myself that I failed at reproducing your issue. Unfortunately, even after the additional report, I am unable to reproduce. This time, I just followed the following steps: - downloaded a .zip from http://jenkins.imagej.net/job/Stable-Fiji/lastSuccessfulBuild/artifact/fiji-win64.zip - unpacked it onto the Desktop - ran ImageJ-win64.exe from there - it wanted to update ij-core, which I let it do. - restarted as suggested - called up the updater again - it said "up-to-date!" As I spent already some time on this issue today, I might have to shift additional endeavors to fix your problem to another day, based on your feedback. For the record: it would be good if you sent your response by logging in to http://fiji.sc/bugzilla/show_bug.cgi?id=585. Our BugZilla is not set up to understand response mails. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ ImageJ-devel mailing list [email protected] http://imagej.net/mailman/listinfo/imagej-devel
