Well,I was speaking of calling the callLater() in the constructor.Anyway, things mess up when they get complicated, you are not doing anything complicated.My main point is, if I had time, I could find the bug and fix it using the framework and callLater(measure) does not need to be used.
Sorry,
I think I understand your point, but those events are also called "at
random" by rolling over elements and such, aren't they? I guess the
way I see it is that we are just faking a rollOver :)
Ben
--- In flexcoders@yahoogroups.com, "Michael Schmalle"
<[EMAIL PROTECTED]> wrote:
>
> Hi Ben,
>
> Wel
Hi Ben,Well you know what, people have called me extreme, can you believe that?! ;-)Anyway, I am totally an advocate of callLater(), just not using callLater() with the framework template methods.IE
- commitProperties()- measure()- updateDisplayList()Think about it this way, the LayoutManager th
Thanks Darron! That works beautifully. Although I can't believe you
don't think SuperCheckBox is an accurate name :)
Michael, I would be interested in hearing your rationale, because so
far it seems like a perfectly valid way of dealing with the underlying
processes of Flash/Flex.
Thanks all,
Ben
heh,Ok, now that I have looked at it a second I see what you are saying. Don't have enough time to test this but, I still think using callLater() for anything that deals with the framework is a no-no.I mean if it gets it to work for you and that is all you need, fine. If you are actually tieing
You know,I replied with the same exact post saying to migrate everything into createChildren();IMHO, you should never call callLater() on a protected method. There is just something seriously wrong with that path.
I don't know but, I tried it with the create children and set the width (to get it
It's not actually the events that are giving you a problem, but rather
it's the tricky nature of dealing with auto-sizing text measurement.
Add this statement to your measure function:
trace( "textHeight = " + textField.textHeight );
trace( "height = " + textField.height );
When the components
Hey,I will look at this and come up with an answer. :)I just guessed. ;-)Peace, MikeOn 9/6/06, ben.clinkinbeard <
[EMAIL PROTECTED]> wrote:
Hi Michael,
Unfortunately, that code didn't help :( They still end up on top of
each other.
I am dispatching the newChil
Hi Michael,
Unfortunately, that code didn't help :( They still end up on top of
each other.
I am dispatching the newChildAdded event in the method that sets the
textField to autoSize and wordWrap to true so that I can call
invalidateDisplayList() in the parent VBox. Without that call the VBox
see
Relooked at your code, wondering why are you doing this:
> > measuredMinHeight = measuredHeight = this.textField.height;Is it really required? I think, its not neccessary and because of that your code is not working. You are right, textField might not have initialized.. But I think, measurement
Thanks for the reply Abdul. However, if I remove the
FlexEvent.CREATION_COMPLETE listener, the checkboxes overlap each
other. Until I roll over them that is... once I roll over them they
each pop into the correct, non-overlapping position. I believe the
problem is that the textbox has not yet resiz
11 matches
Mail list logo
