Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-using events in nested state machines results is 'duplicate' method #146

Closed
Nava2 opened this issue Aug 26, 2015 · 2 comments
Closed
Assignees
Labels
stateMachines Related to state machine syntax, semantics, diagrams or code generation Type-Defect

Comments

@Nava2
Copy link
Contributor

Nava2 commented Aug 26, 2015

Originally reported on Google Code with ID 246
Owned by @obahy


The "e1" is creating two "events", resulting in duplicate methods.

class StateMachineTest {
status {
S1 {
e1 -> S1A;
S1A {
e1 -> S1;
}
}
}
}


Reported by @aforward on 2011-12-01 14:32:13

@Nava2
Copy link
Contributor Author

Nava2 commented Aug 26, 2015

I am raising this to critical simply because we need to prepare for the demo next week,
and time is very short. It does not cause the rest of Umple to fail, but this is simply
a request for Omar to drop everything to fix it.


Reported by @umple on 2011-12-01 14:46:06

  • Labels added: Priority-Critical, stateMachines
  • Labels removed: Priority-High

@Nava2
Copy link
Contributor Author

Nava2 commented Aug 26, 2015

r1078, r1079

I grabbed the latest code, and things worked well.


Reported by @aforward on 2011-12-06 01:54:53

  • Status changed: Fixed

@Nava2 Nava2 added Type-Defect Status-Fixed stateMachines Related to state machine syntax, semantics, diagrams or code generation labels Aug 26, 2015
@Nava2 Nava2 closed this as completed Aug 26, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stateMachines Related to state machine syntax, semantics, diagrams or code generation Type-Defect
Projects
None yet
Development

No branches or pull requests

2 participants