Message View Exception
I found the following exception when I tried to create a message to the same lifeline:
Exception in thread "Animation Thread" java.lang.IndexOutOfBoundsException: Index: 1, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at ca.mcgill.sel.ram.ui.views.message.LifelineView.getFragmentContainerAt(LifelineView.java:639) at ca.mcgill.sel.ram.ui.handler.message.impl.LifelineViewHandler.processTapAndHoldEvent(LifelineViewHandler.java:102) at ca.mcgill.ram.ui.handler.BaseHandler.processGestureEvent(BaseHandler.java:93) at ca.mcgill.sel.ram.ui.views.message.LifelineView$Spacer$1.processGestureEvent(LifelineView.java:127) at org.mt4j.input.GestureEventSupport.fire(GestureEventSupport.java:184) at org.mt4j.input.GestureEventSupport.fireGestureEvt(GestureEventSupport.java:169) at org.mt4j.components.MTComponent.processGestureEvent(MTComponent.java:3033) at org.mt4j.input.inputProcessors.componentProcessors.AbstractComponentProcessor.fireGestureEvent(AbstractComponentProcessor.java:236) at org.mt4j.input.inputProcessors.componentProcessors.AbstractCursorProcessor.fireGestureEvent(AbstractCursorProcessor.java:169) at org.mt4j.input.inputProcessors.componentProcessors.tapAndHoldProcessor.TapAndHoldProcessor.pre(TapAndHoldProcessor.java:155) at org.mt4j.input.inputProcessors.componentProcessors.tapAndHoldProcessor.TapAndHoldProcessor.processAction(TapAndHoldProcessor.java:342) at org.mt4j.AbstractMTApplication.runApplication(AbstractMTApplication.java:327) at org.mt4j.AbstractMTApplication.draw(AbstractMTApplication.java:272) at processing.core.PApplet.handleDraw(PApplet.java:1603) at processing.core.PApplet.run(PApplet.java:1502) at java.lang.Thread.run(Thread.java:695)
Comments (5)
-
-
reporter - attached Networking.ram
- attached Networking.jucm
- attached Networking.core
I uploaded the model. It happens in the message view of getReceiver, when I tried to create a self-message inside the compound fragment.
-
Looking just at the code it appears that an assumption is made on the resulting pick list. However, this error might occur in certain cases when there are problems visualizing combined fragments.
-
- changed status to resolved
Resolved in issue
#194. -
-
assigned issue to
-
assigned issue to
- Log in to comment
It works for me. Do you have a model to reproduce this or if not, steps to reproduce this problem?