I think we don't have any "initComplete" at renderer level, so most of the
times only way is to use addedToParent.
Maybe would be good to add a hook instead of overriding that method.
El jue., 11 jun. 2020 a las 18:20, Alex Harui ()
escribió:
> IMO, it would be best to not require adding
IMO, it would be best to not require adding addedToParent in a script.
It could be that, because most Flex components were set up to be itemrenderers,
that mx Container and a few others should have a default IBeadController of
ItemRendererMouseController specified in MXRoyale defaults.css.
I made a few adjustments to support using the IItemRendererProvider
interface on Menu with UIComponent based renderers.
Then I was able to use a mxml defined mx:HBox based renderer, and have
successfully used it (with some layout tweaks) with some legacy content.
With the approach so far, I still
Pretty sure AdvancedDataGrid supports assignable custom itemrenderers based on
UIComponent. Might be a bit more work for Menu/MenuBar as the current
renderers are not UIComponents.
HTH,
-Alex
On 6/10/20, 1:50 AM, "Greg Dove" wrote:
Hi - probably another question for Alex, unless Yishay
Hi - probably another question for Alex, unless Yishay you have something
similar you have faced here:
For mx.controls.Menu :
specifically for :
set itemRenderer
AFAICS I don't think this is hooked up to take precedence over the default
css IItemRendererFactory for the class, which is picked up
