Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .
Issue Details (XML | Word | Printable)

Key: ECLIPSE-310
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Unassigned
Reporter: Claus Ibsen
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Fuse IDE

Adding a 2nd route, and dragging EIPs on the 2nd route does not work

Created: 13/Jul/11 12:57 PM   Updated: 27/Jul/11 04:34 PM
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0

File Attachments: None
Image Attachments:

1. 2nd-route.png
(88 kB)
Environment: 1.1.77


 Description  « Hide
See screenshot. The top route is the 1st and existing route.

Then I dragged a 2nd route on the canvas, using the route icon from the palette.
And when I drag eg an endpoint on the 2nd route, it seems to be added to the 1st route, there is a wireframe.

Also if I explicit select the 2nd route to make it have focus, and drag EIPs to it, it wont work either.

PS: Maybe when you drag a 2nd route on the canvas, that 2nd route should automatic be selected/focused.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Claus Ibsen added a comment - 13/Jul/11 01:01 PM
If you use the right click -> add route instead then it works. Then you can drag EIPs on the 2nd route.

James Strachan added a comment - 27/Jul/11 04:26 PM
If you click the layout button after dropping the endpoint on the route 2, it does actually work. Its more an issue that the X,Y coords of the newly dropped endpoint don't seem to match where it is relative to the route2 I think. Still trying to figure out whats wrong...

James Strachan added a comment - 27/Jul/11 04:34 PM
turns out it was an issue however many routes you had - it was more if you move the route around, it wasn't setting the absolute X,Y coords of the newly dropped pattern to its actual size relative to the route you drop it into. i.e. it was using the X,Y coords relative to the route as the actual screen coords; so seemed to appear on route 1 (or whatever was at the top of the screen).

fixed in 1.1.83 or later