Thanks for stopping by and adding your 2 cents.

I used clone to get my custom properties also.

import flash.events.Event;

public class AlignControlEvent extends Event
{
public var ControlName:String;
public var ControlType:String;

public static const ALIGN_CONTROL_EVENT:String = “alignControlEvent”;
public function AlignControlEvent(type:String, bubbles:Boolean=false, cancelable:Boolean=false)
{
super(type, bubbles, cancelable);
}
public override function clone():Event
{
var objAlignControlEvent:AlignControlEvent;
objAlignControlEvent = new AlignControlEvent(this.type, this.bubbles, this.cancelable);
objAlignControlEvent.ControlName = this.ControlName;
objAlignControlEvent.ControlType = this.ControlType;

return objAlignControlEvent;
}

}

while dispatching
var objAlignControlEvent:AlignControlEvent = new AlignControlEvent(AlignControlEvent.ALIGN_CONTROL_EVENT);
objAlignControlEvent.ControlType = this._type;
objAlignControlEvent.ControlName = this._name;
dispatchEvent(objAlignControlEvent);

And in handling i read them as
var objA:AlignControlEvent;
objA = (e as AlignControlEvent);
Alert.show(”[align control] [name]” objA.ControlName ” [type]” objA.ControlType) ;

[Event(name="navButtonClicked", type="mx.events.ItemClickEvent")]

and a function:
public function navButtonsEvent():void {
dispatchEvent(new Event(”navButtonClicked”));
}

and the buttonbar:

In my component module I have (not complete, just testing):
public function navButtons(event:ItemClickEvent):void {
var whichButton:int = event.index;
switch(whichButton) {
case 0:
focusManager.setFocus(discrepancyItems[0]);
break;
case 1:
focusManager.setFocus(discrepancyItems[0]);
break;
case 2:
focusManager.setFocus(discrepancyItems[0]);
break;
case 3:
focusManager.setFocus(discrepancyItems[discrepancyCount]);
break;
}
}

What do I need to add where for the component module to see the button click?

I couldn’t retrieve the code posted, and I’m doing this part of the code in actionscript so MXML isn’t really relevant.

For future reference, code placed within a “code” tag should appear ok in the comments.

you can even do something like this

or since event gets passed in

@Eric - The reason I NEED to do this is I’m generating a form element based on the currently selected item in a combobox. Now that formitem is intelligent in that it knows what combobox and the selected item of that combobox that will trigger it’s display. But this information needs to make it into the eventListener so it can determine whether the correct item is selected. Hopefully that clarifies why I need to send the parameters along with the event. Have you got any suggestions for other ways of achieving the same thing?

As for tight coupling, well the combobx is generated within the same class as the privately declared dictionary - which too me is perfectly fine. Pragmatism has to take charge at some stage, and I see nothing wrong with declaring a private variable in a class that will then be referenced by a combobox created in that same class. That’s more like logical coupling to me.

I am setting up my Dictionary with true as it’s constructor parameter.

@Chris and Tink - I did add a clone method, still no cigar. And I realised that my initial dispatch was the only thing that was carrying the parameters along to the eventListener (hence this post).

To me extending a component to pass parameters along seems like overkill in this situation. But I’m glad to know that seems to be the approach required for future issues I may run into.

Juts because a custom event is created and dispatched immediately, it doesn’t have any effect on the event that the ComboBox will despatch when its selectedIndex is changde. When this happens, an Event.CHANGE is dispatched.

If you wanted to dispatch a custom event you would have to do what Eric stated and extend ComboBox, and dispatch you own event where ever the Event.CHANGE was dispatched.

Thats said, like Eric also mentioned this isn’t a great solution, although I guess we don’t fully know the reasons behind it.

Eric