Comments on: Blocking TabBar Click/Change Events

By: iron

iron — Mon, 11 Oct 2010 16:34:18 +0000

txs for this post, very useful, works fine and saved me a lot of work.

By: Kevin

Kevin — Wed, 11 Aug 2010 18:59:22 +0000

All this time…. I actually thought I had tried it without the parentheses but apparently I did not. That did the trick. condition={tabChange}

Your explanation was spot on. It was calling the function and getting the result.

Thanks!

By: Aaron Hardy

Aaron Hardy — Wed, 11 Aug 2010 18:43:23 +0000

Kevin, try replacing this:

condition=”tabChange()”

with this:

condition=”{tabChange}”

As you have it, it will be executing the function tabChange() and sending the return value (in your case, false) into the condition property. What you want is the actual function reference to be set into the condition property so it can be executed at a later time. Let me know how that works out for you.

In response to your other question, you could implement your condition logic inside the same BlockableTabBar class, but I wouldn’t recommend it. Having the condition logic outside lets you keep the BlockableTabBar class generic and usable in many different contexts.

By: Kevin

Kevin — Wed, 11 Aug 2010 18:37:32 +0000

I am trying to use BlockableTabBar and I am having trouble with “condition.” In my file where I am implementing the control i set condition=”tabChange()” where tabChange returns boolean. When I run my code I get TypeError: Error #1034: Type Coercion failed: cannot convert false to Function.

I have BlockableTabBar as a separate AS class. Am I supposed to implement my logic in the class? I am very new to Flex development and on my current project I am handling mostly the .NET middle tier.

Thanks,
Kevin

By: Doug

Doug — Thu, 15 Apr 2010 17:29:25 +0000

Thank you very much, Aaron.

By: Aaron Hardy

Aaron Hardy — Thu, 15 Apr 2010 14:47:47 +0000

I know something, but your best bet is to post your question to FlexCoders: http://tech.groups.yahoo.com/group/flexcoders/

By: Doug

Doug — Thu, 15 Apr 2010 13:56:04 +0000

Hey, Aaron I was, too, brief with my description of my problem; however, another Flex expert has already solved my rollOver problem. Thank you so much. Do you know anything about loading RSS feed containing images and text from a remote Website to a Flex 3 application, and the content update everyday?

By: Aaron Hardy

Aaron Hardy — Thu, 15 Apr 2010 02:55:50 +0000

@Doug
I just did a simple test and the mouseover and mouseout events seem to be working fine even before clicking a link on a linkbar.

By: Doug

Doug — Wed, 14 Apr 2010 17:37:46 +0000

Hello, Aaron

In Flex 3, my mouseOvers & mouseOuts on my LinkBar will not operate until the LinkButtons on the LinkBar have been clicked. Is there a way to get my Overs and Outs to operate after my page loads? My LinkBar is using a dataProvider to display the LinkButtons. Thank You.

By: Aaron Hardy

Aaron Hardy — Sat, 06 Feb 2010 02:46:33 +0000

@Craig

Your method of finding the destination index works. You can simplify it a bit: var selectedIndex:uint= TabBar(event.currentTarget).getChildIndex(event.target as DisplayObject);

Also, I tried redispatching the event like you were attempting to do before. It works fine but you need to dispatch the event off the object that dispatched it in the first place rather than the tabbar itself. Just do this: myEvent.target.dispatchEvent(myEvent);

As far as the LinkBar goes, it’s essentially the same concept but should actually be easier because I don’t think it has any “simulated click trigger” event to deal with. I’d start by overriding LinkBar’s clickHandler() function. Then I’d only call super.clickHandler() if the conditional function returned true, that is, it’s okay to proceed with the navigation.

Hope that helps.