<html>
<head>
<base href="http://fiji.sc/bugzilla/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:hinerm@gmail.com" title="Mark Hiner <hinerm@gmail.com>"> <span class="fn">Mark Hiner</span></a>
</span> changed
<a class="bz_bug_link
bz_status_CONFIRMED "
title="CONFIRMED - java.lang.NullPointerException Analyse Skeleton"
href="http://fiji.sc/bugzilla/show_bug.cgi?id=1105">bug 1105</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>CONFIRMED
</td>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>hinerm@gmail.com, imagej-bugs@imagej.net
</td>
</tr>
<tr>
<td style="text-align:right;">Assignee</td>
<td>imagej-bugs@imagej.net
</td>
<td>ignacio.arganda@gmail.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_CONFIRMED "
title="CONFIRMED - java.lang.NullPointerException Analyse Skeleton"
href="http://fiji.sc/bugzilla/show_bug.cgi?id=1105#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_CONFIRMED "
title="CONFIRMED - java.lang.NullPointerException Analyse Skeleton"
href="http://fiji.sc/bugzilla/show_bug.cgi?id=1105">bug 1105</a>
from <span class="vcard"><a class="email" href="mailto:hinerm@gmail.com" title="Mark Hiner <hinerm@gmail.com>"> <span class="fn">Mark Hiner</span></a>
</span></b>
<pre>This behavior can be confirmed by running Analyze Skeleton on an large-ish
image like the sample MRI Stack.
The tagged skeleton pops up immediately but the results table takes a
significant amount of time to appear. If the tagged skeleton image is closed
before the results table pops, an NPE is thrown.
I think the perfect world solution would be:
1) reporting progress events, perhaps per plane?
and either:
2a) avoiding the NPE if the tagged skeleton image is closed before the analysis
is completed (that is, allowing clean aborts)
or
2b) preventing the tagged skeleton image from being closed before analysis is
completed
But how you want to handle this is up to you Ignacio, as I wouldn't call either
of these "bugs", just inconveniences.
If you think there's something going on in Fiji that's causing the algorithm to
take longer than expected though - let us know!</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>