Re: [flexcoders] mx:ToggleButtonBar / mx:Button

Tue, 29 Aug 2006 17:07:17 -0700

Yup! Sounds good to me, hope Adobe Flex team members hear it :)

-abdul

On 8/29/06, Michael Schmalle < [EMAIL PROTECTED]> wrote:

The interface actually would be;

INavBarClient

Peace, Mike



On 8/28/06, Michael Schmalle <[EMAIL PROTECTED] > wrote:
Hi,


<mx:ToggleButtonBar x="10" y="60" width="640" height="202">
<mx:Array>
<mx:Button label="Button 1" />
<mx:Button label="Button 2" />
<mx:Button label="Button 3" />
</mx:Array>
</mx:ToggleButtonBar>



That said,

Wouldn't it be even more intuitive to just do;

<mx:ToggleButtonBar x="10" y="60" width="640" height="202">
  <mx:Button label="Button 1" />
  <mx:Button label="Button 2" />
  <mx:Button label="Button 3" />
</mx:ToggleButtonBar>
Like it is actually a container, which it is.

The implementation hard codes Button in a whole bunch of NavBar and subclasses with casting.

If they made this the way of the container, it would allow anything unless they type check which ironically they are as Button.

I think in updates, the use of more UI interfaces will help here.

Like any child of the NavBar(button item) has to be of interface INavBar.

interface INavBar
{
   function get selected():Boolean;
   function set....
   function get toggle():Boolean;
   function set...
   etc... All these interface properties would be what is dependent in the NavBar implementation.
}

I have run into this problem with the TabBar and the Button casting and it's a pain in the ... :)

Peace, Mike




Peace, Mike

 






On 8/28/06, Abdul Qabiz < [EMAIL PROTECTED]> wrote:

<mx:ToggleButtonBar x="10" y="60" width="640" height="202">
<mx:Array>
<mx:Button label="Button 1" />
<mx:Button label="Button 2" />
<mx:Button label="Button 3" />
</mx:Array>
</mx:ToggleButtonBar>


I know that sounds more intuitive. Hopefully, next version would have update on it..

I remember, we actually did things that way while we were designing ButtonBar/ToggleButtonBar. But we changed it to current implementation later for some reasons.

-abdul




On 8/24/06, Michael Schmalle < [EMAIL PROTECTED]> wrote:

Hi,

You don't put components in a dataProvider. The ButtonBar reads from the model of a dataProvider which has for example a label property in the list of objects.

You can also just specify an array of strings to be the label names. The ButtonBar will always use a Button for it's button. ;-)

Peace, Mike



On 8/22/06, Gunther < [EMAIL PROTECTED]> wrote:

Why does the following code throws an exception:

Error: ERROR: The dataProvider of 'a ToggleButtonBar' must be
String, ViewStack, Array, or IList.

<mx:ToggleButtonBar x="10" y="60" width="640" height="202">
<mx:Array>
<mx:Button label="Button 1" />
<mx:Button label="Button 2" />
<mx:Button label="Button 3" />
</mx:Array>
</mx:ToggleButtonBar>

If I use this code:

<mx:ToggleButtonBar x="10" y="60" width="640" height="202">
<mx:Array>
<mx:String>Test</mx:String>
<mx:Button label="Button 1" />
<mx:Button label="Button 2" />
<mx:Button label="Button 3" />
</mx:Array>
</mx:ToggleButtonBar>

There is no problem ??

I want to make a toggable button bar where each button is skinnable
and has the possibility for an up/down/selected image.






--
What goes up, does come down.





--
What goes up, does come down.



--
What goes up, does come down.


__._,_.___

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Software development tool Software development Software development services
Home design software Software development company

YAHOO! GROUPS LINKS



__,_._,___

Reply via email to