Macromedia Flash Server - List Component Scrolling Issue

Author

List Component Scrolling Issue

Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@publi

2005-06-17, 5:45 pm

I'm populating an instance of the list component with a dataProvider. The
dataProvider stores users who have logged in. If someone logs in, an
onSync triggers the dataProvider to be copied to a temporary array, the
name is added, and then the temporary array is copied back to the
dataProvider using the following:

tempArray.dispatchEvent({target:permanentArray,
type:"modelChanged"});

The list is updated appropriately.

If someone logs out, the same thing happens. Based on the "code" property
of that user's SharedObject slot, the name is deleted from the temporary
array, then the temporary array is copied back again using the same
dispatchEvent.

Once again, the list is updated appropriately.

The problem is when I scroll the list component, ONLY AFTER a name has
been DELETED from the dataProvider. One particular cell label will
duplicate itself and fill the entire list. If the list is refreshed based
on someone logging in or out, the list is refreshed and the correct
usernames show up again. Until then, it's all one name. Likewise, if I
log in at that moment, the list appears as it should. It only happens
when scrolling.

Can't figure it out. I don't believe the dataProvider could be changed
based on scrolling the list, but the cells are somehow being changed.

Thanks again,
Brandon

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

JesterXL

2005-06-17, 5:45 pm

How are you adding and remove dudes from the list? DataProvider has an API
that's pretty strict... and tricky.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:12 PM
Subject: [FlashComm] List Component Scrolling Issue

I'm populating an instance of the list component with a dataProvider. The
dataProvider stores users who have logged in. If someone logs in, an
onSync triggers the dataProvider to be copied to a temporary array, the
name is added, and then the temporary array is copied back to the
dataProvider using the following:

tempArray.dispatchEvent({target:permanentArray,
type:"modelChanged"});

The list is updated appropriately.

If someone logs out, the same thing happens. Based on the "code" property
of that user's SharedObject slot, the name is deleted from the temporary
array, then the temporary array is copied back again using the same
dispatchEvent.

Once again, the list is updated appropriately.

The problem is when I scroll the list component, ONLY AFTER a name has
been DELETED from the dataProvider. One particular cell label will
duplicate itself and fill the entire list. If the list is refreshed based
on someone logging in or out, the list is refreshed and the correct
usernames show up again. Until then, it's all one name. Likewise, if I
log in at that moment, the list appears as it should. It only happens
when scrolling.

Can't figure it out. I don't believe the dataProvider could be changed
based on scrolling the list, but the cells are somehow being changed.

Thanks again,
Brandon

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@publi

2005-06-17, 5:45 pm

To oversimplify the process:

attendanceList.dataProvider = this.allUserNames;

Each user has their own Shared Object slot. When someone new logs in or
out, the onSync fires.

I copy the dataProvider array to a temp array:

var dp = this.allUserNames;

If the user is new, he/she gets added to the temp array. If someone has
left the meeting, he/she is deleted from the temp array. Nothing should
happen at this point to the list.

The list is updated when I dispatch the event to the "this.allUserNames"

dp.dispatchEvent({target:this.allUserNames, type:"modelChanged"});

Make sense?

Thanks.

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:17 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

How are you adding and remove dudes from the list? DataProvider has an
API
that's pretty strict... and tricky.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:12 PM
Subject: [FlashComm] List Component Scrolling Issue

I'm populating an instance of the list component with a dataProvider. The
dataProvider stores users who have logged in. If someone logs in, an
onSync triggers the dataProvider to be copied to a temporary array, the
name is added, and then the temporary array is copied back to the
dataProvider using the following:

tempArray.dispatchEvent({target:permanentArray,
type:"modelChanged"});

The list is updated appropriately.

If someone logs out, the same thing happens. Based on the "code" property
of that user's SharedObject slot, the name is deleted from the temporary
array, then the temporary array is copied back again using the same
dispatchEvent.

Once again, the list is updated appropriately.

The problem is when I scroll the list component, ONLY AFTER a name has
been DELETED from the dataProvider. One particular cell label will
duplicate itself and fill the entire list. If the list is refreshed based
on someone logging in or out, the list is refreshed and the correct
usernames show up again. Until then, it's all one name. Likewise, if I
log in at that moment, the list appears as it should. It only happens
when scrolling.

Can't figure it out. I don't believe the dataProvider could be changed
based on scrolling the list, but the cells are somehow being changed.

Thanks again,
Brandon

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

JesterXL

2005-06-17, 5:45 pm

Aye. Don't do that. Use the DataProvider API.

Aka:
- adding a user:

allUserNames.addItem("person");

- removing a user

allUserNames.removeItemAt(2);

- user changes name

allUserNames.replaceItemAt(2, "person2");

When using removeAll, make sure you wait a frame before adding other things.
DataProvider has its modelChanged queued, so it'll only broadcast once per
frame, so you don't have to worry about sending too many change requests to
the List.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:23 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

To oversimplify the process:

attendanceList.dataProvider = this.allUserNames;

Each user has their own Shared Object slot. When someone new logs in or
out, the onSync fires.

I copy the dataProvider array to a temp array:

var dp = this.allUserNames;

If the user is new, he/she gets added to the temp array. If someone has
left the meeting, he/she is deleted from the temp array. Nothing should
happen at this point to the list.

The list is updated when I dispatch the event to the "this.allUserNames"

dp.dispatchEvent({target:this.allUserNames, type:"modelChanged"});

Make sense?

Thanks.

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:17 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

How are you adding and remove dudes from the list? DataProvider has an
API
that's pretty strict... and tricky.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:12 PM
Subject: [FlashComm] List Component Scrolling Issue

I'm populating an instance of the list component with a dataProvider. The
dataProvider stores users who have logged in. If someone logs in, an
onSync triggers the dataProvider to be copied to a temporary array, the
name is added, and then the temporary array is copied back to the
dataProvider using the following:

tempArray.dispatchEvent({target:permanentArray,
type:"modelChanged"});

The list is updated appropriately.

If someone logs out, the same thing happens. Based on the "code" property
of that user's SharedObject slot, the name is deleted from the temporary
array, then the temporary array is copied back again using the same
dispatchEvent.

Once again, the list is updated appropriately.

The problem is when I scroll the list component, ONLY AFTER a name has
been DELETED from the dataProvider. One particular cell label will
duplicate itself and fill the entire list. If the list is refreshed based
on someone logging in or out, the list is refreshed and the correct
usernames show up again. Until then, it's all one name. Likewise, if I
log in at that moment, the list appears as it should. It only happens
when scrolling.

Can't figure it out. I don't believe the dataProvider could be changed
based on scrolling the list, but the cells are somehow being changed.

Thanks again,
Brandon

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@publi

2005-06-17, 5:45 pm

I did it the other way to eliminate the number of changes sent to the
dataProvider. Like in this tutorial:
http://flash-communications.net/tec...rays/index.html

What do you think?

Plus, other changes could be happening. Users can change their own slots.
The dataProvider also holds the "state" of the user. Each entry contains
Username and State. If either one is updated, the whole dataProvider
needs to be updated because the list needs to be updated as well.

I'm actually doing as you have pointed out, but to the temporary array. Is
dispatchEvent not recommended? I know I don't really need it if I update
the dataProvider directly. Just by updating it, the list will be updated.
Correct?

Thanks,
Brandon

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:32 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

Aye. Don't do that. Use the DataProvider API.

Aka:
- adding a user:

allUserNames.addItem("person");

- removing a user

allUserNames.removeItemAt(2);

- user changes name

allUserNames.replaceItemAt(2, "person2");

When using removeAll, make sure you wait a frame before adding other
things.
DataProvider has its modelChanged queued, so it'll only broadcast once per

frame, so you don't have to worry about sending too many change requests
to
the List.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:23 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

To oversimplify the process:

attendanceList.dataProvider = this.allUserNames;

Each user has their own Shared Object slot. When someone new logs in or
out, the onSync fires.

I copy the dataProvider array to a temp array:

var dp = this.allUserNames;

If the user is new, he/she gets added to the temp array. If someone has
left the meeting, he/she is deleted from the temp array. Nothing should
happen at this point to the list.

The list is updated when I dispatch the event to the "this.allUserNames"

dp.dispatchEvent({target:this.allUserNames, type:"modelChanged"});

Make sense?

Thanks.

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:17 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

How are you adding and remove dudes from the list? DataProvider has an
API
that's pretty strict... and tricky.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:12 PM
Subject: [FlashComm] List Component Scrolling Issue

I'm populating an instance of the list component with a dataProvider. The
dataProvider stores users who have logged in. If someone logs in, an
onSync triggers the dataProvider to be copied to a temporary array, the
name is added, and then the temporary array is copied back to the
dataProvider using the following:

tempArray.dispatchEvent({target:permanentArray,
type:"modelChanged"});

The list is updated appropriately.

If someone logs out, the same thing happens. Based on the "code" property
of that user's SharedObject slot, the name is deleted from the temporary
array, then the temporary array is copied back again using the same
dispatchEvent.

Once again, the list is updated appropriately.

The problem is when I scroll the list component, ONLY AFTER a name has
been DELETED from the dataProvider. One particular cell label will
duplicate itself and fill the entire list. If the list is refreshed based
on someone logging in or out, the list is refreshed and the correct
usernames show up again. Until then, it's all one name. Likewise, if I
log in at that moment, the list appears as it should. It only happens
when scrolling.

Can't figure it out. I don't believe the dataProvider could be changed
based on scrolling the list, but the cells are somehow being changed.

Thanks again,
Brandon

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

JesterXL

2005-06-17, 5:45 pm

I agree with the article's theory on softening the strain of onSync. I do
disagree with the implementation; you do not need to utilize push and
generate your own modelChanged event. Merely use the methods itself;
DataProvider is decently efficient to only update the View once per frame.

Again, using replaceItemAt, you are not updating the whole thing, just one
slot. There are fine grained events that tell Views how to handle the
changes, and what parts have changed so it doesn't need to redraw itself
entirely. DataGrid and List do a pretty good job at this.

push does not dispatch modelChanged.

addItem does.

Therefore, call addItem, and know it'll only ever be issued once per frame.

If you have to refactor because of performance, we can re-look at this, but
I've never had issues with this, but my target platform specs are high so
may differ.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:42 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

I did it the other way to eliminate the number of changes sent to the
dataProvider. Like in this tutorial:
http://flash-communications.net/tec...rays/index.html

What do you think?

Plus, other changes could be happening. Users can change their own slots.
The dataProvider also holds the "state" of the user. Each entry contains
Username and State. If either one is updated, the whole dataProvider
needs to be updated because the list needs to be updated as well.

I'm actually doing as you have pointed out, but to the temporary array. Is
dispatchEvent not recommended? I know I don't really need it if I update
the dataProvider directly. Just by updating it, the list will be updated.
Correct?

Thanks,
Brandon

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:32 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

Aye. Don't do that. Use the DataProvider API.

Aka:
- adding a user:

allUserNames.addItem("person");

- removing a user

allUserNames.removeItemAt(2);

- user changes name

allUserNames.replaceItemAt(2, "person2");

When using removeAll, make sure you wait a frame before adding other
things.
DataProvider has its modelChanged queued, so it'll only broadcast once per

frame, so you don't have to worry about sending too many change requests
to
the List.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:23 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

To oversimplify the process:

attendanceList.dataProvider = this.allUserNames;

Each user has their own Shared Object slot. When someone new logs in or
out, the onSync fires.

I copy the dataProvider array to a temp array:

var dp = this.allUserNames;

If the user is new, he/she gets added to the temp array. If someone has
left the meeting, he/she is deleted from the temp array. Nothing should
happen at this point to the list.

The list is updated when I dispatch the event to the "this.allUserNames"

dp.dispatchEvent({target:this.allUserNames, type:"modelChanged"});

Make sense?

Thanks.

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:17 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

How are you adding and remove dudes from the list? DataProvider has an
API
that's pretty strict... and tricky.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:12 PM
Subject: [FlashComm] List Component Scrolling Issue

I'm populating an instance of the list component with a dataProvider. The
dataProvider stores users who have logged in. If someone logs in, an
onSync triggers the dataProvider to be copied to a temporary array, the
name is added, and then the temporary array is copied back to the
dataProvider using the following:

tempArray.dispatchEvent({target:permanentArray,
type:"modelChanged"});

The list is updated appropriately.

If someone logs out, the same thing happens. Based on the "code" property
of that user's SharedObject slot, the name is deleted from the temporary
array, then the temporary array is copied back again using the same
dispatchEvent.

Once again, the list is updated appropriately.

The problem is when I scroll the list component, ONLY AFTER a name has
been DELETED from the dataProvider. One particular cell label will
duplicate itself and fill the entire list. If the list is refreshed based
on someone logging in or out, the list is refreshed and the correct
usernames show up again. Until then, it's all one name. Likewise, if I
log in at that moment, the list appears as it should. It only happens
when scrolling.

Can't figure it out. I don't believe the dataProvider could be changed
based on scrolling the list, but the cells are somehow being changed.

Thanks again,
Brandon

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

JesterXL

2005-06-17, 5:45 pm

BTW, ignorant of me; which List component are you using; Flash MX 2004 or
the Flashcom ones based off of AS1?

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:42 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

I did it the other way to eliminate the number of changes sent to the
dataProvider. Like in this tutorial:
http://flash-communications.net/tec...rays/index.html

What do you think?

Plus, other changes could be happening. Users can change their own slots.
The dataProvider also holds the "state" of the user. Each entry contains
Username and State. If either one is updated, the whole dataProvider
needs to be updated because the list needs to be updated as well.

I'm actually doing as you have pointed out, but to the temporary array. Is
dispatchEvent not recommended? I know I don't really need it if I update
the dataProvider directly. Just by updating it, the list will be updated.
Correct?

Thanks,
Brandon

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:32 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

Aye. Don't do that. Use the DataProvider API.

Aka:
- adding a user:

allUserNames.addItem("person");

- removing a user

allUserNames.removeItemAt(2);

- user changes name

allUserNames.replaceItemAt(2, "person2");

When using removeAll, make sure you wait a frame before adding other
things.
DataProvider has its modelChanged queued, so it'll only broadcast once per

frame, so you don't have to worry about sending too many change requests
to
the List.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:23 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

To oversimplify the process:

attendanceList.dataProvider = this.allUserNames;

Each user has their own Shared Object slot. When someone new logs in or
out, the onSync fires.

I copy the dataProvider array to a temp array:

var dp = this.allUserNames;

If the user is new, he/she gets added to the temp array. If someone has
left the meeting, he/she is deleted from the temp array. Nothing should
happen at this point to the list.

The list is updated when I dispatch the event to the "this.allUserNames"

dp.dispatchEvent({target:this.allUserNames, type:"modelChanged"});

Make sense?

Thanks.

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:17 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

How are you adding and remove dudes from the list? DataProvider has an
API
that's pretty strict... and tricky.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:12 PM
Subject: [FlashComm] List Component Scrolling Issue

I'm populating an instance of the list component with a dataProvider. The
dataProvider stores users who have logged in. If someone logs in, an
onSync triggers the dataProvider to be copied to a temporary array, the
name is added, and then the temporary array is copied back to the
dataProvider using the following:

tempArray.dispatchEvent({target:permanentArray,
type:"modelChanged"});

The list is updated appropriately.

If someone logs out, the same thing happens. Based on the "code" property
of that user's SharedObject slot, the name is deleted from the temporary
array, then the temporary array is copied back again using the same
dispatchEvent.

Once again, the list is updated appropriately.

The problem is when I scroll the list component, ONLY AFTER a name has
been DELETED from the dataProvider. One particular cell label will
duplicate itself and fill the entire list. If the list is refreshed based
on someone logging in or out, the list is refreshed and the correct
usernames show up again. Until then, it's all one name. Likewise, if I
log in at that moment, the list appears as it should. It only happens
when scrolling.

Can't figure it out. I don't believe the dataProvider could be changed
based on scrolling the list, but the cells are somehow being changed.

Thanks again,
Brandon

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@publi

2005-06-17, 5:45 pm

MX 2004

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 02:06 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

BTW, ignorant of me; which List component are you using; Flash MX 2004 or
the Flashcom ones based off of AS1?

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:42 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

I did it the other way to eliminate the number of changes sent to the
dataProvider. Like in this tutorial:
http://flash-communications.net/tec...rays/index.html

What do you think?

Plus, other changes could be happening. Users can change their own slots.
The dataProvider also holds the "state" of the user. Each entry contains
Username and State. If either one is updated, the whole dataProvider
needs to be updated because the list needs to be updated as well.

I'm actually doing as you have pointed out, but to the temporary array. Is
dispatchEvent not recommended? I know I don't really need it if I update
the dataProvider directly. Just by updating it, the list will be updated.
Correct?

Thanks,
Brandon

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:32 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

Aye. Don't do that. Use the DataProvider API.

Aka:
- adding a user:

allUserNames.addItem("person");

- removing a user

allUserNames.removeItemAt(2);

- user changes name

allUserNames.replaceItemAt(2, "person2");

When using removeAll, make sure you wait a frame before adding other
things.
DataProvider has its modelChanged queued, so it'll only broadcast once per

frame, so you don't have to worry about sending too many change requests
to
the List.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:23 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

To oversimplify the process:

attendanceList.dataProvider = this.allUserNames;

Each user has their own Shared Object slot. When someone new logs in or
out, the onSync fires.

I copy the dataProvider array to a temp array:

var dp = this.allUserNames;

If the user is new, he/she gets added to the temp array. If someone has
left the meeting, he/she is deleted from the temp array. Nothing should
happen at this point to the list.

The list is updated when I dispatch the event to the "this.allUserNames"

dp.dispatchEvent({target:this.allUserNames, type:"modelChanged"});

Make sense?

Thanks.

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:17 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

How are you adding and remove dudes from the list? DataProvider has an
API
that's pretty strict... and tricky.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:12 PM
Subject: [FlashComm] List Component Scrolling Issue

I'm populating an instance of the list component with a dataProvider. The
dataProvider stores users who have logged in. If someone logs in, an
onSync triggers the dataProvider to be copied to a temporary array, the
name is added, and then the temporary array is copied back to the
dataProvider using the following:

tempArray.dispatchEvent({target:permanentArray,
type:"modelChanged"});

The list is updated appropriately.

If someone logs out, the same thing happens. Based on the "code" property
of that user's SharedObject slot, the name is deleted from the temporary
array, then the temporary array is copied back again using the same
dispatchEvent.

Once again, the list is updated appropriately.

The problem is when I scroll the list component, ONLY AFTER a name has
been DELETED from the dataProvider. One particular cell label will
duplicate itself and fill the entire list. If the list is refreshed based
on someone logging in or out, the list is refreshed and the correct
usernames show up again. Until then, it's all one name. Likewise, if I
log in at that moment, the list appears as it should. It only happens
when scrolling.

Can't figure it out. I don't believe the dataProvider could be changed
based on scrolling the list, but the cells are somehow being changed.

Thanks again,
Brandon

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

JesterXL

2005-06-17, 5:45 pm

Yeah man, you're good to go then, MX 2004 has a pretty good DataProvider -
List combo of being efficient to DataProvider changes.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 2:11 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

MX 2004

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 02:06 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

BTW, ignorant of me; which List component are you using; Flash MX 2004 or
the Flashcom ones based off of AS1?

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:42 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

I did it the other way to eliminate the number of changes sent to the
dataProvider. Like in this tutorial:
http://flash-communications.net/tec...rays/index.html

What do you think?

Plus, other changes could be happening. Users can change their own slots.
The dataProvider also holds the "state" of the user. Each entry contains
Username and State. If either one is updated, the whole dataProvider
needs to be updated because the list needs to be updated as well.

I'm actually doing as you have pointed out, but to the temporary array. Is
dispatchEvent not recommended? I know I don't really need it if I update
the dataProvider directly. Just by updating it, the list will be updated.
Correct?

Thanks,
Brandon

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:32 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

Aye. Don't do that. Use the DataProvider API.

Aka:
- adding a user:

allUserNames.addItem("person");

- removing a user

allUserNames.removeItemAt(2);

- user changes name

allUserNames.replaceItemAt(2, "person2");

When using removeAll, make sure you wait a frame before adding other
things.
DataProvider has its modelChanged queued, so it'll only broadcast once per

frame, so you don't have to worry about sending too many change requests
to
the List.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:23 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

To oversimplify the process:

attendanceList.dataProvider = this.allUserNames;

Each user has their own Shared Object slot. When someone new logs in or
out, the onSync fires.

I copy the dataProvider array to a temp array:

var dp = this.allUserNames;

If the user is new, he/she gets added to the temp array. If someone has
left the meeting, he/she is deleted from the temp array. Nothing should
happen at this point to the list.

The list is updated when I dispatch the event to the "this.allUserNames"

dp.dispatchEvent({target:this.allUserNames, type:"modelChanged"});

Make sense?

Thanks.

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:17 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

How are you adding and remove dudes from the list? DataProvider has an
API
that's pretty strict... and tricky.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:12 PM
Subject: [FlashComm] List Component Scrolling Issue

I'm populating an instance of the list component with a dataProvider. The
dataProvider stores users who have logged in. If someone logs in, an
onSync triggers the dataProvider to be copied to a temporary array, the
name is added, and then the temporary array is copied back to the
dataProvider using the following:

tempArray.dispatchEvent({target:permanentArray,
type:"modelChanged"});

The list is updated appropriately.

If someone logs out, the same thing happens. Based on the "code" property
of that user's SharedObject slot, the name is deleted from the temporary
array, then the temporary array is copied back again using the same
dispatchEvent.

Once again, the list is updated appropriately.

The problem is when I scroll the list component, ONLY AFTER a name has
been DELETED from the dataProvider. One particular cell label will
duplicate itself and fill the entire list. If the list is refreshed based
on someone logging in or out, the list is refreshed and the correct
usernames show up again. Until then, it's all one name. Likewise, if I
log in at that moment, the list appears as it should. It only happens
when scrolling.

Can't figure it out. I don't believe the dataProvider could be changed
based on scrolling the list, but the cells are somehow being changed.

Thanks again,
Brandon

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@publi

2005-06-17, 5:45 pm

So I can basically maintain the process, except perform the actions on the
dataProvider directly, correct? It's basically just a different array.
What dispatches modelChanged? Just adding, deleting, and changing
entries, correct? Looping through the provider will not refresh the list,
will it?

Thanks,
Brandon

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 02:12 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

Yeah man, you're good to go then, MX 2004 has a pretty good DataProvider -

List combo of being efficient to DataProvider changes.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 2:11 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

MX 2004

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 02:06 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

BTW, ignorant of me; which List component are you using; Flash MX 2004 or
the Flashcom ones based off of AS1?

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:42 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

I did it the other way to eliminate the number of changes sent to the
dataProvider. Like in this tutorial:
http://flash-communications.net/tec...rays/index.html

What do you think?

Plus, other changes could be happening. Users can change their own slots.
The dataProvider also holds the "state" of the user. Each entry contains
Username and State. If either one is updated, the whole dataProvider
needs to be updated because the list needs to be updated as well.

I'm actually doing as you have pointed out, but to the temporary array. Is
dispatchEvent not recommended? I know I don't really need it if I update
the dataProvider directly. Just by updating it, the list will be updated.
Correct?

Thanks,
Brandon

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:32 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

Aye. Don't do that. Use the DataProvider API.

Aka:
- adding a user:

allUserNames.addItem("person");

- removing a user

allUserNames.removeItemAt(2);

- user changes name

allUserNames.replaceItemAt(2, "person2");

When using removeAll, make sure you wait a frame before adding other
things.
DataProvider has its modelChanged queued, so it'll only broadcast once per

frame, so you don't have to worry about sending too many change requests
to
the List.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:23 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

To oversimplify the process:

attendanceList.dataProvider = this.allUserNames;

Each user has their own Shared Object slot. When someone new logs in or
out, the onSync fires.

I copy the dataProvider array to a temp array:

var dp = this.allUserNames;

If the user is new, he/she gets added to the temp array. If someone has
left the meeting, he/she is deleted from the temp array. Nothing should
happen at this point to the list.

The list is updated when I dispatch the event to the "this.allUserNames"

dp.dispatchEvent({target:this.allUserNames, type:"modelChanged"});

Make sense?

Thanks.

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:17 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

How are you adding and remove dudes from the list? DataProvider has an
API
that's pretty strict... and tricky.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:12 PM
Subject: [FlashComm] List Component Scrolling Issue

I'm populating an instance of the list component with a dataProvider. The
dataProvider stores users who have logged in. If someone logs in, an
onSync triggers the dataProvider to be copied to a temporary array, the
name is added, and then the temporary array is copied back to the
dataProvider using the following:

tempArray.dispatchEvent({target:permanentArray,
type:"modelChanged"});

The list is updated appropriately.

If someone logs out, the same thing happens. Based on the "code" property
of that user's SharedObject slot, the name is deleted from the temporary
array, then the temporary array is copied back again using the same
dispatchEvent.

Once again, the list is updated appropriately.

The problem is when I scroll the list component, ONLY AFTER a name has
been DELETED from the dataProvider. One particular cell label will
duplicate itself and fill the entire list. If the list is refreshed based
on someone logging in or out, the list is refreshed and the correct
usernames show up again. Until then, it's all one name. Likewise, if I
log in at that moment, the list appears as it should. It only happens
when scrolling.

Can't figure it out. I don't believe the dataProvider could be changed
based on scrolling the list, but the cells are somehow being changed.

Thanks again,
Brandon

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

JesterXL

2005-06-17, 5:45 pm

Yeah, you change your dataProvider, and the View will automatically update.
Actually, it's a reference to the same array, just using a different name.

If you want to know what dispatches a modelChanged, and what does not, look
at the mixin class yourself:

mx.controls.listclasses.DataProvider

C:\Documents and Settings\[username]\Local Settings\Application
Data\Macromedia\Flash MX
2004\en\Configuration\Classes\mx\control
s\listclasses

Replace [username] with your username. Not sure on a Mac.

Basically, any of the dataProvider API's commands trigger a modelChanged.
push, shift, etc., do not.

Getting data does not dispatch modelChanged events because you aren't
changing things; so using things like getItemAt(3) in a loop are fine. You
could technically use this.array[3] instead if you really really wanted; I
doubt much would change since this is all the DataProvider does:

function getItemAt(index : Number)
{
return this[index];
}

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 2:16 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

So I can basically maintain the process, except perform the actions on the
dataProvider directly, correct? It's basically just a different array.
What dispatches modelChanged? Just adding, deleting, and changing
entries, correct? Looping through the provider will not refresh the list,
will it?

Thanks,
Brandon

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 02:12 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

Yeah man, you're good to go then, MX 2004 has a pretty good DataProvider -

List combo of being efficient to DataProvider changes.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 2:11 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

MX 2004

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 02:06 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

BTW, ignorant of me; which List component are you using; Flash MX 2004 or
the Flashcom ones based off of AS1?

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:42 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

I did it the other way to eliminate the number of changes sent to the
dataProvider. Like in this tutorial:
http://flash-communications.net/tec...rays/index.html

What do you think?

Plus, other changes could be happening. Users can change their own slots.
The dataProvider also holds the "state" of the user. Each entry contains
Username and State. If either one is updated, the whole dataProvider
needs to be updated because the list needs to be updated as well.

I'm actually doing as you have pointed out, but to the temporary array. Is
dispatchEvent not recommended? I know I don't really need it if I update
the dataProvider directly. Just by updating it, the list will be updated.
Correct?

Thanks,
Brandon

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:32 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

Aye. Don't do that. Use the DataProvider API.

Aka:
- adding a user:

allUserNames.addItem("person");

- removing a user

allUserNames.removeItemAt(2);

- user changes name

allUserNames.replaceItemAt(2, "person2");

When using removeAll, make sure you wait a frame before adding other
things.
DataProvider has its modelChanged queued, so it'll only broadcast once per

frame, so you don't have to worry about sending too many change requests
to
the List.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:23 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

To oversimplify the process:

attendanceList.dataProvider = this.allUserNames;

Each user has their own Shared Object slot. When someone new logs in or
out, the onSync fires.

I copy the dataProvider array to a temp array:

var dp = this.allUserNames;

If the user is new, he/she gets added to the temp array. If someone has
left the meeting, he/she is deleted from the temp array. Nothing should
happen at this point to the list.

The list is updated when I dispatch the event to the "this.allUserNames"

dp.dispatchEvent({target:this.allUserNames, type:"modelChanged"});

Make sense?

Thanks.

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:17 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

How are you adding and remove dudes from the list? DataProvider has an
API
that's pretty strict... and tricky.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:12 PM
Subject: [FlashComm] List Component Scrolling Issue

I'm populating an instance of the list component with a dataProvider. The
dataProvider stores users who have logged in. If someone logs in, an
onSync triggers the dataProvider to be copied to a temporary array, the
name is added, and then the temporary array is copied back to the
dataProvider using the following:

tempArray.dispatchEvent({target:permanentArray,
type:"modelChanged"});

The list is updated appropriately.

If someone logs out, the same thing happens. Based on the "code" property
of that user's SharedObject slot, the name is deleted from the temporary
array, then the temporary array is copied back again using the same
dispatchEvent.

Once again, the list is updated appropriately.

The problem is when I scroll the list component, ONLY AFTER a name has
been DELETED from the dataProvider. One particular cell label will
duplicate itself and fill the entire list. If the list is refreshed based
on someone logging in or out, the list is refreshed and the correct
usernames show up again. Until then, it's all one name. Likewise, if I
log in at that moment, the list appears as it should. It only happens
when scrolling.

Can't figure it out. I don't believe the dataProvider could be changed
based on scrolling the list, but the cells are somehow being changed.

Thanks again,
Brandon

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@publi

2005-06-17, 5:45 pm

Thanks. Appreciate it. I will try modifying.

Sorry, one more question. The way I'm doing it now, storing the
dataProvider in a temporary array, is it just inefficient? Just wondering
why you think it's not the best idea, or why you think it could cause
problems.

Thanks,
Brandon

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 02:34 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

Yeah, you change your dataProvider, and the View will automatically
update.
Actually, it's a reference to the same array, just using a different name.

If you want to know what dispatches a modelChanged, and what does not,
look
at the mixin class yourself:

mx.controls.listclasses.DataProvider

C:\Documents and Settings\[username]\Local Settings\Application
Data\Macromedia\Flash MX
2004\en\Configuration\Classes\mx\control
s\listclasses

Replace [username] with your username. Not sure on a Mac.

Basically, any of the dataProvider API's commands trigger a modelChanged.
push, shift, etc., do not.

Getting data does not dispatch modelChanged events because you aren't
changing things; so using things like getItemAt(3) in a loop are fine. You

could technically use this.array[3] instead if you really really wanted; I

doubt much would change since this is all the DataProvider does:

function getItemAt(index : Number)
{
return this[index];
}

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 2:16 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

So I can basically maintain the process, except perform the actions on the
dataProvider directly, correct? It's basically just a different array.
What dispatches modelChanged? Just adding, deleting, and changing
entries, correct? Looping through the provider will not refresh the list,
will it?

Thanks,
Brandon

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 02:12 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

Yeah man, you're good to go then, MX 2004 has a pretty good DataProvider -

List combo of being efficient to DataProvider changes.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 2:11 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

MX 2004

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 02:06 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

BTW, ignorant of me; which List component are you using; Flash MX 2004 or
the Flashcom ones based off of AS1?

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:42 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

I did it the other way to eliminate the number of changes sent to the
dataProvider. Like in this tutorial:
http://flash-communications.net/tec...rays/index.html

What do you think?

Plus, other changes could be happening. Users can change their own slots.
The dataProvider also holds the "state" of the user. Each entry contains
Username and State. If either one is updated, the whole dataProvider
needs to be updated because the list needs to be updated as well.

I'm actually doing as you have pointed out, but to the temporary array. Is
dispatchEvent not recommended? I know I don't really need it if I update
the dataProvider directly. Just by updating it, the list will be updated.
Correct?

Thanks,
Brandon

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:32 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

Aye. Don't do that. Use the DataProvider API.

Aka:
- adding a user:

allUserNames.addItem("person");

- removing a user

allUserNames.removeItemAt(2);

- user changes name

allUserNames.replaceItemAt(2, "person2");

When using removeAll, make sure you wait a frame before adding other
things.
DataProvider has its modelChanged queued, so it'll only broadcast once per

frame, so you don't have to worry about sending too many change requests
to
the List.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:23 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

To oversimplify the process:

attendanceList.dataProvider = this.allUserNames;

Each user has their own Shared Object slot. When someone new logs in or
out, the onSync fires.

I copy the dataProvider array to a temp array:

var dp = this.allUserNames;

If the user is new, he/she gets added to the temp array. If someone has
left the meeting, he/she is deleted from the temp array. Nothing should
happen at this point to the list.

The list is updated when I dispatch the event to the "this.allUserNames"

dp.dispatchEvent({target:this.allUserNames, type:"modelChanged"});

Make sense?

Thanks.

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:17 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

How are you adding and remove dudes from the list? DataProvider has an
API
that's pretty strict... and tricky.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:12 PM
Subject: [FlashComm] List Component Scrolling Issue

I'm populating an instance of the list component with a dataProvider. The
dataProvider stores users who have logged in. If someone logs in, an
onSync triggers the dataProvider to be copied to a temporary array, the
name is added, and then the temporary array is copied back to the
dataProvider using the following:

tempArray.dispatchEvent({target:permanentArray,
type:"modelChanged"});

The list is updated appropriately.

If someone logs out, the same thing happens. Based on the "code" property
of that user's SharedObject slot, the name is deleted from the temporary
array, then the temporary array is copied back again using the same
dispatchEvent.

Once again, the list is updated appropriately.

The problem is when I scroll the list component, ONLY AFTER a name has
been DELETED from the dataProvider. One particular cell label will
duplicate itself and fill the entire list. If the list is refreshed based
on someone logging in or out, the list is refreshed and the correct
usernames show up again. Until then, it's all one name. Likewise, if I
log in at that moment, the list appears as it should. It only happens
when scrolling.

Can't figure it out. I don't believe the dataProvider could be changed
based on scrolling the list, but the cells are somehow being changed.

Thanks again,
Brandon

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

JesterXL

2005-06-17, 5:45 pm

Well, you are not storing it; it's merely a reference. Array's and objects
made like this:

var a:Array = myOtherArray;

"a" and "myOtherArray" are the same thing, just different pointers.
However:

var b:String = "something";
var c:String = b;

"c" and "b" in this case are 2 totally different things. Notice:

myOtherArray = ["one", "two", "three"];
var a:Array = myOtherArray;

var b:String = "something";
var c:String = b;
c += " else";

trace(myOtherArray); // one,two,three
a.push("moo");
trace(myOtherArray); // one,two,three,moo

trace(b); // something
trace(c); // something else
delete b;
trace(b); // undefined
trace(c); // something else

So, temporarey arrays are not what you think they are in that case. There
is no clone method either in ActionScript, and making one is challenging
because as you know Array's can hold other arrays, thus making it extremely
hard if you have a deeply nested RecordSet or something.

In conclusion:

yourArray, var a = yourArray, and yourList.dataProvider are all the same
thing.

The difference is, if you NEVER set a dataProvider to your List component,
it by default has it's own internal one that is delete when you do
yourList.dataProvider. Afterwards, all 3 are the same thing.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 2:59 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

Thanks. Appreciate it. I will try modifying.

Sorry, one more question. The way I'm doing it now, storing the
dataProvider in a temporary array, is it just inefficient? Just wondering
why you think it's not the best idea, or why you think it could cause
problems.

Thanks,
Brandon

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 02:34 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

Yeah, you change your dataProvider, and the View will automatically
update.
Actually, it's a reference to the same array, just using a different name.

If you want to know what dispatches a modelChanged, and what does not,
look
at the mixin class yourself:

mx.controls.listclasses.DataProvider

C:\Documents and Settings\[username]\Local Settings\Application
Data\Macromedia\Flash MX
2004\en\Configuration\Classes\mx\control
s\listclasses

Replace [username] with your username. Not sure on a Mac.

Basically, any of the dataProvider API's commands trigger a modelChanged.
push, shift, etc., do not.

Getting data does not dispatch modelChanged events because you aren't
changing things; so using things like getItemAt(3) in a loop are fine. You

could technically use this.array[3] instead if you really really wanted; I

doubt much would change since this is all the DataProvider does:

function getItemAt(index : Number)
{
return this[index];
}

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 2:16 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

So I can basically maintain the process, except perform the actions on the
dataProvider directly, correct? It's basically just a different array.
What dispatches modelChanged? Just adding, deleting, and changing
entries, correct? Looping through the provider will not refresh the list,
will it?

Thanks,
Brandon

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 02:12 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

Yeah man, you're good to go then, MX 2004 has a pretty good DataProvider -

List combo of being efficient to DataProvider changes.

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 2:11 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

MX 2004

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 02:06 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

BTW, ignorant of me; which List component are you using; Flash MX 2004 or
the Flashcom ones based off of AS1?

----- Original Message -----
From: <Brandon_Krakowsky-A5pIpylr7pFSljaRc5+PrA@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Cc: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>;
<flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
Sent: Friday, June 17, 2005 1:42 PM
Subject: Re: [FlashComm] List Component Scrolling Issue

I did it the other way to eliminate the number of changes sent to the
dataProvider. Like in this tutorial:
http://flash-communications.net/tec...rays/index.html

What do you think?

Plus, other changes could be happening. Users can change their own slots.
The dataProvider also holds the "state" of the user. Each entry contains
Username and State. If either one is updated, the whole dataProvider
needs to be updated because the list needs to be updated as well.

I'm actually doing as you have pointed out, but to the temporary array. Is
dispatchEvent not recommended? I know I don't really need it if I update
the dataProvider directly. Just by updating it, the list will be updated.
Correct?

Thanks,
Brandon

"JesterXL" <jesterxl-RyEax5csP4NCVeB36W80OQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
06/17/2005 01:32 PM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>

To
"FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc

Subject
Re: [FlashComm] List Component Scrolling Issue

Aye. Don't do that. Use the DataProvider API.

Aka:
- adding a user:

allUserNames.addItem("person");

- removing a user

allUserNames.removeItemAt(2);

- user changes name

allUserNames.replaceItemAt(2, "person2");

When using removeAll, make sure you wait a frame before adding