NOTICE! This is a static HTML version of a legacy Fiji BugZilla bug.

The Fiji project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Bug 83 - "Drag and Drop" fails once after Fiji start on Mac
"Drag and Drop" fails once after Fiji start on Mac
Status: RESOLVED LATER
Product: Fiji
Classification: Unclassified
Component: Other
unspecified
Macintosh Mac OS
: P2 minor
Assigned To: ImageJ Bugs Mailing List
Depends on:
Blocks:
 
Reported: 2009-09-27 15:29 CDT by Jan Eglinger
Modified: 2009-10-02 16:48 CDT
1 user (show)

See Also:

Description Jan Eglinger 2009-09-27 15:29:52 CDT
When dragging a (tif) file to the status bar after starting Fiji, the status bar changes to "<<Drag and Drop>>", but no file is opened. Dragging a second time opens the file as expected.

Note: dragging to the tool bar always works, only the status bar seems affected. Dragging to the dock icon works as well.
(tried with updated Fiji/ImageJ 1.43g on Mac OS X 10.5.8)

Can anybody reproduce this bug?
Comment 1 G. Landini 2009-09-27 17:42:25 CDT
(In reply to comment #0)
> When dragging a (tif) file to the status bar after starting Fiji, the status
> bar changes to "<<Drag and Drop>>", but no file is opened. Dragging a second
> time opens the file as expected.

Works OK for me *so far* under linux.
In ImageJ, the drag and drop works fine *most of the time*, but something sometimes happens and it stops working.
Other people have reported this, but unfortunately nobody seems to be able to pinpoint what exactly triggers this lack of response.
I wonder if these two problems are related.
Comment 2 Johannes Schindelin 2009-09-27 19:26:50 CDT
I saw that, yes, and a _preliminary_ debug run said that Java did not offer _any_ type for the drop the first time, but miraculously worked beautifully the next time.

Maybe somebody else saw the same issue and found a workaround...
Comment 3 Jean-Yves Tinevez 2009-09-28 08:57:32 CDT
> 
> Can anybody reproduce this bug?
> 
I can, reproducibly, under Mac OS X 10.5.8.
Comment 4 Johannes Schindelin 2009-09-28 23:57:22 CDT
Is it possible that it works always (even the first time) if you drop on the toolbar instead of the status bar?
Comment 5 Jean-Yves Tinevez 2009-09-29 08:58:09 CDT
(In reply to comment #4)
> Is it possible that it works always (even the first time) if you drop on the
> toolbar instead of the status bar?

Amazing. Yes.
I can be even more precise:

- if i drop it directly on the status bar, it does not open (the first time)
- if i drop it on the tool bar, it opens
- if i drop it on the status bar, by passing it first over the tool bar, it opens

Comment 6 Johannes Schindelin 2009-09-29 11:46:55 CDT
I tried myself now on a very beefy machine, and it seems to have gone away: could you try with http://pacific.mpi-cbg.de/snaps/ij.jar, please?
Comment 7 Jan Eglinger 2009-09-29 11:57:35 CDT
> I tried myself now on a very beefy machine, and it seems to have gone away:
> could you try with http://pacific.mpi-cbg.de/snaps/ij.jar, please?
> 
No, the problem persists, at least on my system (MacOSX 10.5). I replaced ./Fiji.app/ij.jar by your file, but still: status bar doesn't work at first time, tool bar always works...

jan
Comment 8 Jean-Yves Tinevez 2009-09-29 12:01:17 CDT
same symptoms with the new ij.jar
Comment 9 Johannes Schindelin 2009-09-29 12:54:05 CDT
Do y'all have 32-bit Macs?  I.e. is it Java6 or Java5?
Comment 10 Jan Eglinger 2009-09-29 13:22:52 CDT
> Do y'all have 32-bit Macs?  I.e. is it Java6 or Java5?
> 

No, 64-bit. Sorry, forgot to mention that (Java 1.6.0_13)

jan
Comment 11 Johannes Schindelin 2009-10-01 19:24:08 CDT
I saw it happening on a computer where some accessibility thingie was switched on (which is apparently needed for AppleScripts to run).  Reading the source, there is only one thing I could imagine to be responsible: setDropTarget(null).  Could you try again with http://pacific.mpi-cbg.de/snaps/ij.jar?  This one has said command commented out.
Comment 12 Jan Eglinger 2009-10-01 23:00:54 CDT
>  Could you try again with http://pacific.mpi-cbg.de/snaps/ij.jar?  This one has
> said command commented out.
> 
I have to disappoint you, still the same problem. So far I tried it on a Mac Pro and a MacBook with rather standard OSX 10.5.8 installations on them, no special accessibility options. Very strange...
Comment 13 Johannes Schindelin 2009-10-02 16:48:42 CDT
Okay, so it works on the same machine when forcing Java 1.5.  I claim that this cannot be helped, except by waiting for Apple to get their act together.  Well, they should not have forked from Sun's JDK that heavily, I guess.