Who would have thought that the humble Text component could be so
full of bugs?!
Here's one that giving me trouble at the moment:
?xml version=1.0 encoding=utf-8?
mx:Application xmlns:mx=http://www.adobe.com/2006/mxml;
mx:Script
![CDATA[
to the
application, rather than relative to the target.
Hmm.
- Tom
n51red wrote:
Interesting.
One option is to set the x and y attribes of the tooltips in the
toolTipShown event handler of the relevant component. The event
handler
might look like:
event.toolTip.x = xPos;
event.toolTip.y
Interesting.
One option is to set the x and y attribes of the tooltips in the
toolTipShown event handler of the relevant component. The event handler
might look like:
event.toolTip.x = xPos;
event.toolTip.y = yPos;
Could you let me know what you come up with?
Thanks,
Nick
--- In
Hello,
Somebody asked me to provide an example of how to use arbirary
components as tool tips. So here goes:
Notes
-
For a component to be used as a tooltip it must implement the IToolTip
interface. I've used a base class (CustomToolTip) for the custom
tooltips in this example that takes
This bug is with Adobe now. A workaround it to set the minHeight
property of the text components.
--- In flexcoders@yahoogroups.com, n51red [EMAIL PROTECTED] wrote:
Hello,
I'm in the process of migrating an appliation from flex 2 beta 3 to
the
flex 2 final release and I have come accross
I remember read a few days ago that these
invisible components can't be styled.
I seems you've been mislead Carlos. Components like HBox and VBox are
invisible by default, but styles like backgroundColor do work.
Hank's suggestion about using nesting works well (see example), but
has
Turns out this error was occuring because name of the focusManager
variable in the focusOnInput() function was clashing with the
mx.core.UIComponent.focusManager property. So the problem was
resolved by renaming the variable.
--- In flexcoders@yahoogroups.com, n51red [EMAIL PROTECTED] wrote
I wouldn't say that. The issue is that containers carry with them a
substantial processing burden. So it you've got a lot of components
visible (say, 20 or 30) with borders added to them in this way, you may
start to notice a lag as the components are rendered.
N51
--- In
Hello,
Sorry to bump, but there seems to be a something lack of information
around on the usage of the FocusManger. Does anyone have any advice
on this issue?
Thank you,
N51
--- In flexcoders@yahoogroups.com, n51red [EMAIL PROTECTED] wrote:
Hello,
After migrating an application from f2b3
Hello,
I'm in the process of migrating an appliation from flex 2 beta 3 to the
flex 2 final release and I have come accross a new problem with
adjacent text components inside VBoxes. It appears that when the
positions of the text components are recalculated they momentarily
appear on top of
Hello,
After migrating an application from f2b3 to the final release of Flex
2 a new problem has emerged involving the FocusManager.
I use a FocusManager to focus on a TextInput when its parent becomes
visible. The text input does indeed take the focus and the component
responds to the
Do you have a simple test case ?
The following code demonstrates the problem:
?xml version=1.0 encoding=utf-8?
mx:Application xmlns:mx=http://www.adobe.com/2006/mxml;
layout=absolute
mx:Style
Application{
backgroundColor:white;
color:black;
}
.boxStyle1{
I think so too. Thanks for looking into it.
N51
--- In flexcoders@yahoogroups.com, Tom Chiverton [EMAIL PROTECTED]
wrote:
On Friday 30 June 2006 14:56, n51red wrote:
think
I think that's a bug, replicates here easily.
Send it to Adobe :-)
--
Tom Chiverton
Of n51red
Sent: Thursday, June 22, 2006 3:22 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: htmlText formating destroyed by binding
execution
Forgive my rudeness in bumping this post but this problem is a
persistent nusance I like would like to find out what's going
Forgive my rudeness in bumping this post but this problem is a
persistent nusance I like would like to find out what's going on.
...And should have mentioned that I'm referring to f2b3.
--- In flexcoders@yahoogroups.com, n51red [EMAIL PROTECTED] wrote:
I've come across some odd behaviour
I've come across some odd behaviour with Text components that have the
htmlText attribute in use. If a binding execution causes the text to
change while some of that text is selected, the text styles revert to
their defaults, ignoring values set either inline or in CSS. I assume
this is a
Is there any mechanism for multithreading in Flex(2.0), such that
client side processing can continue without freezing the user interface?
Thanks,
N51
Yahoo! Groups Sponsor ~--
Home is just a click away. Make Yahoo! your home page now.
-Original Message-
From: flexcoders@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of n51red
Sent: Friday, June 02, 2006 9:20 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] f2b3 custom ToolTip troubles
I've been replacing tool tips with arbitrary IUComonents
this with adobe engineer and the answer is :
this
feature won't be supported.
the work around here is using getter/setter.
On 5/30/06, n51red [EMAIL PROTECTED] wrote:
I have come accross a problem in which certain data bindings
invoving
static varaibles produce bizarre compilation errors
I've been replacing tool tips with arbitrary IUComonents by
intersepting the toolTipCreate method and changing the toolTip property
to my component. This works quite well except for when the tooltip is
does not have room to appear to the bottom left of the cursor. In this
situation the the
I have come accross a problem in which certain data bindings invoving
static varaibles produce bizarre compilation errors.
All the bindings that have caused problems have taken a form similar
to this:
booleanVariable={myInstance.variable==MyClass.staticVariable}
Each instance of the problem
Is it possible to make branch nodes behave the same as leaf nodes in
response to a mouse click, that is, close the menu and fire a change
event?
I assume such events a fired 'behind the scenes' and are canceled some
where along the hierarchy.
I'm thinking of trying expand the MenuBar class
listen to the mouseUp handler and dispatch your
own change
event, and also call the public funtion hide(). I haven't tried it,
but it
should work. You could refer the mouseUpHandler code in Menu for
some help.
Thanks,
Anant.
On 5/11/06, n51red [EMAIL PROTECTED] wrote:
Is it possible
anything wrong. Wait a few more days
for B3 where I believe we've fixed a lot of menu problems.
Matt
-Original Message-
From: flexcoders@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of n51red
Sent: Thursday, May 04, 2006 5:59 AM
To: flexcoders@yahoogroups.com
Subject
Hello,
I'm new to flex but haev an object orientated background.
I'm trying to populate a MenuBar with data from a data structure I've
implemented.
This data structure revolves round a class I've called Category that
contains an ArrayCollection of child Categories. I've been attmpting
to
25 matches
Mail list logo
