Hi Manish,

Your trick doesn't seem to work. Actually it throws an exception on app. init.

Debugging the thumbnail.mxml file I observe the following:

1. first thumbnail ' function set dataObject'  is called with dataObject corresponding to dataprovider[0] multiple times
2. when it do iterates over the dataProvider array, both 'label', and parent is null? (which is what causes the exception)
3. 'function set dataObject' is _not_ called when the dataProvider array is changed.

I also notice that the binding works when tiles are scrolled off, and on screen. I presume this is caused by the tiles being destroyed/created when not in view/being displayed anew and therefore not related to anything useful.

Isn't there a way to loop through the itemlist, and manually force a rebind of the dataObjects?

I guess one could rebind the dataProvider by alternating 2 databuffers; but how do i clone the object array. Object itself doesn't seem to implement .clone() ? Do I have to write some for..in stuff for that?

I'll tell you, I for one is hoping for a new release _very_ soon.  :D

cheers

 -michael






On 11/19/05, Manish Jethani <[EMAIL PROTECTED] > wrote:
On 11/18/05, Michael Hansen <[EMAIL PROTECTED]> wrote:

>  I don't quite follow your suggestion. Sorry for being stupid, but all this
> is semi new to me :) Could you elaborate a bit on your  answer?

So instead of this:

<mx:Vbox>
    <mx:Image source="./{dataObject.file"  />
    <mx:Label text="{dataObject.file}"/>
</mx:VBox>

You have to do this:

<mx:Vbox>
    <mx:Image source="./{dataObject.file"  />
    <mx:Label id="label" />
    <mx:Script>
      override public function set dataObject(value:Object):Void
      {
        super.dataObject = value;
        label.text = value.file;
      }
    </mx:Script>
</mx:VBox>

Which sucks obviously, but for the time being that's what we have
(wait for the next build).

>  Also do you guys have a public bug tracking running somewhere. I would save
> us all (both you and me) some time. (i also got found 7 or 8 bugs i would
> like verify, before submitting)

No, I don't think so.  I'm sure QA engineers from the Flex team are
lurking on the list (and often posting too) and will pick up any
problems reported here.

Manish


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




YAHOO! GROUPS LINKS






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




YAHOO! GROUPS LINKS




Reply via email to