Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8820963
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 14, 20262026-06-14T05:44:15+00:00 2026-06-14T05:44:15+00:00

I have a NetStream which is put into data generation mode properly… everything works

  • 0

I have a NetStream which is put into data generation mode properly… everything works fine and I get onSeekPoint() events when I do something like the following:

EXAMPLE 1

public function setupStream() {
     netStream.client = {};
     netStream.client.onSeekPoint = this.onSeekPoint;
     netStream.client.onMetaData = this.onMetaData;
}

public function onSeekPoint(... args) {...}
public function onMetaData(... args) {...}

However, instead of keeping it all in that parent class, I need to create a new class for the client which also has that onSeekPoint. It doesn’t work. Strangely, the onMetaData callback does… it’s something like this:

EXAMPLE 2

package {
   public class CustomClient {
       public function CustomClient() {
       }
       public function onSeekPoint(... args) {...}
       public function onMetaData(... args) {...}
   }
}

public function setupStream() {
   var myClient:CustomClient = new CustomClient();
   netStream.client = CustomClient;
}

I thought that maybe there’s some small issue I missed- but what’s really freaking me out, is that this fully works properly…

EXAMPLE 3

package {
   public class CustomClient {
       public function CustomClient() {
       }
       public function onSeekPoint(... args) {...}
       public function onMetaData(... args) {...}
   }
}

public function setupStream() {
   var myClient:CustomClient = new CustomClient();
   netStream.client = {};
   netStream.client.onSeekPoint = myClient.onSeekPoint;
   netStream.client.onMetaData = myClient.onMetaData
}

I guess “if it ain’t broke don’t fix it” might apply here, but I’m a little worried letting some code I don’t understand go, and afraid it might come back to bite me when I least expect it 😉

My questions are:

  1. Why doesn’t the second example work for seekPoints?
  2. Ok then- why does the second example work for metaData?
  3. Why does the third example fix everything?

EDIT: In case it’s unclear, the different classes are correctly in separate files, etc. They’re just combined in the examples here to make it easier to digest

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-14T05:44:16+00:00Added an answer on June 14, 2026 at 5:44 am

    In your second example you have this:

    var myClient:CustomClient = new CustomClient();
    netStream.client = CustomClient;
    

    But shouldn’t it be something like this:

    var myClient:CustomClient = new CustomClient();
    netStream.client = myClient;
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have some FLVs which I'd like to play. The following code works fine
I have this little NetStream movie (which I'm not allowed to show, sorry) set
I have an application which uses SslStream to send and receive data with its
I have a TcpClient object which sends some data to server, using its underlying
i have a data service hosted in azure from which i am sending notification
I have a flex 3 app that uses netstream and a video object to
have written this little class, which generates a UUID every time an object of
Have a procedure which looks like Procedure TestProc(TVar1, TVar2 : variant); Begin TVar1 :=
Have deployed numerous report parts which reference the same view however one of them
I have a user control UserControl which is in an assembly Assembly. I have

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.