Fix Bdv too frequent navigation deadlock

[stefanhahmann]

This PR contains a strategy to avoid to frequent navigation requests to the Big Data Viewer, which cause Mastodon to get stuck in certain sitations.

It is not the actual bug fix (that probably needs to be done in Big Data Viewer), but a work around to avoid the Big Data Viewer to get into this bug.

Fixes #371

Improvements to navigation frequency control:

• Added a lastNavigationTime field to track the timestamp of the last navigation request and prevent navigation requests that occur too frequently. This logic was implemented in both navigateToVertex and navigateToEdge methods. [1] [2] [3] [4]

[Copilot]

Pull Request Overview

A workaround to prevent excessive navigation requests to the Big Data Viewer by enforcing a minimum delay between actions, reducing the chance of deadlock.

• Introduces lastNavigationTime and a constant ANIMATION_DURATION to throttle rapid successive navigations.
• Applies throttle checks in both navigateToVertex and navigateToEdge, and replaces hard-coded 300 ms durations with the new constant.

Comments suppressed due to low confidence (2)

src/main/java/org/mastodon/views/bdv/overlay/OverlayNavigation.java:129

• After allowing a navigation in navigateToEdge, lastNavigationTime is never updated. Add lastNavigationTime = now; immediately after the throttle check to correctly record the timestamp for subsequent calls.

			panel.setTransformAnimator( animator );

src/main/java/org/mastodon/views/bdv/overlay/OverlayNavigation.java:51

• [nitpick] Consider renaming ANIMATION_DURATION to something like NAVIGATION_THROTTLE_MS or ANIMATION_DURATION_MS to clarify that it serves both as the animation duration and the cooldown interval.

	private static final int ANIMATION_DURATION = 300;

[tinevez]

This is an horrid bug and a sensitive part of the code.
I would like to have the review of @tpietzsch here instead of mine.

[tpietzsch]

I'll look at it during the celltrackathon

[stefanhahmann]

Just a reminder, since users seem to be running into this bug quite frequently, when heavily using mastodon..

@tinevez @tpietzsch

[tinevez]

I will merge it now and make a new release.
We can go back to this PR if we need to revert it should a fix in the upstream code be done.