Community
Participate
Working Groups
Build Identifier: I believe this is caused by the way in which Graphiti implements copy/paste, using the Eclipse (SWT) clipboard, and because the copied objects in the clipboad adapt to IFile (or IResource). Perhaps this should be considered in some more global copy/paste functionality redesign, if deemed appropiate. Related discussion in the forum: http://www.eclipse.org/forums/index.php/mv/msg/246748/737250/ Reproducible: Always Steps to Reproduce: 1. In the tutorial, create som some graphical object/s in the Graphical editor and copy it/them. 2. Go to the Navigator (or Project Explorer), with the project or any other element selected, right-click for the context-menu 3. The Paste command is enabled, and when executed it tries to copy the file.
Created attachment 213016 [details] Proposed patch Only uses FileTransfer and ResourcesTransfer if any of the selected elements can adapt to IFile, or is the only element contained in that IFile.
Thanks for the contribution! I have checked-in the patch and pushed it to Eclipse: commit a36b594ba6316e4aeb608b3c8a2df98c70b553f9 Author: mwenz <michael.wenz@sap.com> 2012-03-26 15:31:02 Committer: mwenz <michael.wenz@sap.com> 2012-03-26 15:31:02 Parent: b86ed73db2028058344bdd3b18a8057d7fa754df (Bug 374918 - Let default paste use LocalSelectionTransfer) Branches: origin/master, master
After having a closer look, I think the clipboard and the copy/paste functionality deserve a clean-up (probably after the Juno release). I have opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=375334 for that.
Bookkeeping: Set target release
Part of Graphiti 0.9.0 (Eclipse Juno)