tag:robotlegs.tenderapp.com,2009-10-18:/discussions/problems/16-event-name-collisionsRobotlegs: Discussion 2013-04-28T10:03:25Ztag:robotlegs.tenderapp.com,2009-10-18:Comment/6535042009-12-01T01:03:38Z2009-12-01T01:03:38ZEvent name collisions<div><p>It's an event name collision from initial glance. Both constants
have the same value of "SAVE".</p>
<p>I'm sure others may have an opinion on this, but I use the
following naming convention to avoid this problem...</p>
<pre>
<code>public class PaletteEvent
extends Event
{
public static const OPEN:String = "PaletteEvent.OPEN";
public static const EXPAND:String = "PaletteEvent.EXPAND";
public static const COLLAPSE:String = "PaletteEvent.COLLAPSE";
...</code>
</pre>
<p>A similar approach may solve your problem.</p></div>derekdontag:robotlegs.tenderapp.com,2009-10-18:Comment/6535042009-12-02T08:17:29Z2009-12-02T08:17:29ZEvent name collisions<div><p>It's a collision. You could use the naming technique suggested
above, or preferably:</p>
<p>Use the 4th parameter of mapListener to ensure that your
listeners only respond to events of the correct class.</p></div>Shaun Smith