Calling commitProperties directly will work but after that if this
component gets added then it is not showing display list properly. Instead
of creating news rows and align them properly it keeps on putting
everything on first row itself.
Best Regards
Pawan
On Thu, Mar 12, 2015 at 9:45 AM, Jake
Hi Jeffry,
*Why wouldn't you just call commitProperties() directly?*
commitProperties() is a protected method.
The OP stated that he is working with *some UIComponent *and that he
changed public properties such as *includeInLayout= false *and
*selectedItem**. *I took this to mean he is asking ho
On 3/11/2015 10:38 PM, Jake Knerr wrote:
//
To the OP: if you don't want to extend the component, you should be
able to get commitProperties() to fire on a component that has not
been added to the displayList by first calling invalidateProperties()
and then call validateProperties().
*E.G.*
*If it isn't on the stage; then invalidateProperties will have no affect;
because the SystemManager (is that the right class?) is not aware of it;
and will push the component through its validation process.*
I didn't realize that the component hadn't been added to the displayList.
Serves me right
Just a quick note to advise that since a new flash 17 beta release today, I
experienced a failure at "Validating download" of playerglobal.swc
I expect this needs a new hash to compare against in the installer config
(might be wrong here)
Anybody feel like taking on a TLF bug? I’ve been poking at
https://issues.apache.org/jira/browse/FLEX-34769 over the past several
days.
It appears that the code that resets _startComposePosition means that the
test case now composes many more lines than it used to. It used to
compose each line o
On 3/11/2015 1:01 PM, Jake Knerr wrote:
Try calling invalidateProperties() before calling validateNow() to get
commitProperties() to fire.
If it isn't on the stage; then invalidateProperties will have no
affect; because the SystemManager (is that the right class?) is not
aware of it; and will
I did a simple test that worked for me. In the creationComplete handler
of a simple app, I did this:
private function testNestLevel():void
{
var s:TextArea = new TextArea();
s.nestLevel = 2;
s.validateNow();
}
In the debugger, I saw validateNow go into the TextArea’
No luck, It didn't work with nestLevel = 2.
Not getting any call in commitproperties method through validateNow()
Best Regards
Pawan
On Wed, Mar 11, 2015 at 8:40 PM, Alex Harui wrote:
>
> On 3/11/15, 7:50 AM, "Jeffry Houser" wrote:
>
> >
> > I did this back in "the day" when creating the wa
On 3/11/15, 7:50 AM, "Jeffry Houser" wrote:
>
> I did this back in "the day" when creating the watermark I used for
>Flextras components. I basically created a component, rendered it, and
>turned it into a bitmap before ever putting it on the stage.
>
> I had to write my own routine to force
I did this back in "the day" when creating the watermark I used for
Flextras components. I basically created a component, rendered it, and
turned it into a bitmap before ever putting it on the stage.
I had to write my own routine to force the component to go through
it's life cycle w/o b
Hi Dany,
Vast en zeker!
We welcome all contributions and there is no reason why we wouldn't
include yours.
When Om (or another committer...) gets a chance to commits your patch
to 'develop', I'll be glad to cherry pick it into the release branch.
EdB
On Wed, Mar 11, 2015 at 3:29 PM, Dany Dho
Extend the component to use a custom data object as its data source. So
update the commit properties and lifecycle functions to get the current
data from the object.
Then what you have to ensure is that your data object is live, rather than
worrying about the component.
2015-03-11 11:30 GMT-03:00
Hi Eric,
Would the patch I made for FLEX-34772 make it to this release?
@OM: did you manage to have a look at my patch already?
thx,
Dany
Op 11 mar 2015 om 08:56 uur uur schreef Erik de Bruin :
Hi all,
Due to the overwhelming response to the imminent 4.14.1 release, I
only now have time to
Hi - Is it possible to maintain some UIComponent with adding it to any
parent component.
I need to keep mx in hidden state but want to update the data into it like
selected item. Since it is not added to any parent component that's why its
commit properties methods is not getting called.
I know I
I think it is, yes. I wrote as many unit tests I could think of to
verify it, hopefully they're inclusive enough.
I found this bug while writing the unit tests to verify the fix for
this one[1]. I don't think I'm able to finish work on it this week,
but next week for sure. If it's not too late, ma
Hi all,
Due to the overwhelming response to the imminent 4.14.1 release, I
only now have time to give the Installer some love :-P
I have cut the release branch and started the release builds on the Builds VM.
I think we're waiting on Nick to land his contribution, as well as
some verification th
Mihai,
I'd love to add this to the 4.14.1 release. Do you think it is stable
enough for inclusion?
EdB
On Tue, Mar 10, 2015 at 5:43 PM, wrote:
> FLEX-34778
> CAUSE: When a node is opened, HierarchicalCollectionView starts to listen to
> changes to its children collection. And when it's clos
This test:
mobile/components/ActionBar/styles/ActionBar_Styles
ActionBar_TitleDisplay_TextDecoration Failed CompareBitmap(body:step
2) compare returned[object BitmapData]
Is now the only one consistently failing during the 'mobile' Mustella runs.
The 'bad' files can be found here:
http://flex-
19 matches
Mail list logo
