That's interesting that Steve mentioned autoLayout. We had a similar
problem with a bunch of image rollovers that were all flickering as a group,
and it turned out to be that because we hadn't told them their height or
width, they were having to lay themselves out to find out - hence the
flicker
If you have a Text field with selectable text, it's possible to scroll the
content by clicking on the text and dragging downwards. This leaves (in one
simple case I've made) the top line of text obscured, and an apparent blank
line at the bottom.
Is there any way to prevent this without making
*Short version:*
I have a non-visual component that I'm trying to declare in a repeater, but
it seems that MXML doesn't allow this. Is this true? How do you get around
this, create a visual component to wrap the non-visual component?
*Long version:*
I have an ActionScript non-visual component
have an
appropriate interface for the context you are placing it in. e.g. It should
be a IUIComponent.
http://livedocs.adobe.com/flex/201/langref/mx/core/IUIComponent.html
Rick Winscot
On 12/12/08 12:49 PM, Michael Prescott michael.r.presc...@gmail.com
wrote:
*Short version:
*
I
for the context you are placing it in. e.g. It should
be a IUIComponent.
http://livedocs.adobe.com/flex/201/langref/mx/core/IUIComponent.html
Rick Winscot
On 12/12/08 12:49 PM, Michael Prescott michael.r.presc...@gmail.com
wrote:
*Short version:
*
I have a non-visual component that I'm trying
] *On
Behalf Of *Michael Prescott
*Sent:* Friday, December 12, 2008 11:17 AM
*To:* flexcoders@yahoogroups.com
*Subject:* Re: [flexcoders] Restrictions on non-visual component placement
It still seems to be true.
Yes, I can see that before repeaters are involved, but the detail popup
creates
When is it that you have to implement measure()? If you're building
components in MXML, purely out of other standard Flex components, do you
ever need to bother with measure()?
I'm making an MXML item renderer, and I'm running into some trouble with the
DataGrid handling the variable row height
/private/hjd33kkztkuojpzltd2ylw
You can use mx:component to do thins kind of like this, but
mx:component defines classes, not interfaces, and IIRC, mxmlc is kinda
picky as to where it'll let you do it.
-Josh
On Tue, Dec 9, 2008 at 10:53 AM, Michael Prescott
[EMAIL PROTECTED] wrote:
Sweet
Is it possible to define a component but somehow cause it to be omitted from
the enclosing component's list of children? Essentially:
mx:VBox
mx:Label text=This is added as a child of the vbox, as normal./
mx:Label visible=false text=This is invisible.. but is there some way
to not have it
Of *Michael Prescott
*Sent:* Monday, December 08, 2008 4:28 PM
*To:* flexcoders@yahoogroups.com
*Subject:* [flexcoders] Defining, but not adding to parent in MXML
Is it possible to define a component but somehow cause it to be omitted
from the enclosing component's list of children? Essentially
*Why* it's different I can't tell you, but if you're being regularly
surprised, it sounds like you might benefit from skimming through the
language reference. This behavior is described on the
, but I think it happened to me a couple of times
and the result is that the databinding simply does not fire for any changes
after the null in the chain.
Do a simple test app and try it out. it will be faster than you looking for
the doc.
On Fri, Nov 28, 2008 at 12:01 PM, Michael Prescott
Is there any reference material that describes how Flex behaves when it
encounters a null part way along a data binding chain?
Michael
at 11:12 PM, Amy [EMAIL PROTECTED] wrote:
--- In flexcoders@yahoogroups.com flexcoders%40yahoogroups.com,
Michael Prescott
[EMAIL PROTECTED] wrote:
I'm having some troubles with data binding and a named event
generated
by a custom non-visual component. What I'm trying to do is have
I haven't come across this, but I heartily recommend upgrading to 3.0.2 if
you haven't already.
On Tue, Nov 25, 2008 at 3:21 PM, wkolcz [EMAIL PROTECTED] wrote:
I like to start my AS files by adding all the import statement of all
the items I know I am going to need.
However, if I forget
I'm having some troubles with data binding and a named event generated
by a custom non-visual component. What I'm trying to do is have a
property (say, 'data') which, when it changes, triggers the usual
data-binding updates, but also fires an event that can be listened to
in the MXML. For
16 matches
Mail list logo