Unexpected behavior when multiple objects have the same name
Reported by David Cox | February 24th, 2009 @ 10:23 PM | in 0.4.4
This needs to be investigated further to determine if it is still a problem. New problems may also have arisen at the borders between what I was doing and what Ben was doing.
Need to especially check actions with same names (action names should be irrelevant), and task system states.
Comments and changes to this ticket
-
David Cox February 25th, 2009 @ 03:01 PM
- State changed from “new” to “resolved”
Marionette tests for this appear to be passing.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
The core framework and supporting libraries for the MWorks Suite
David Cox