i don't know if the switch command is different in flex than flash, but that's incorrect syntax for using switch in flash.  look in the api to see the correct way to use switch in flex.

thank you, _sp.

op:

correct use is:

switch(o.command){

case somevalue:

//some code

break;

case someothervalue:

//some other code

break;

//etc

}

-

Man I hate when these forums won't let you edit. I read the post wrong.

try needs a catch or finally. It needs to know what to "do" when it fails.

e.g.:

try

{

     // this

}

catch (e)

{

     // error occured, do something if you want

}

kglad initially helped you so you should mark him as correct answer and you can just mark mine as helpful.

You should declare them at the top of your class and they all need an access modifier. Such as private, protected, internal, public.

e.g.

package {
 
    import flash.display.Sprite; 
 
    public class MyClass extends Sprite {
 
        // define your variables here
         private var NewValue:String;  // create a variable only this class can use by marking it private
 
        // constructor
        public function MyClass() {
                NewValue = "Some String"; // set the initial value
         }
 
        private function SomeFunction():void
         {
               // this function is in this class so I can modify NewValue
                NewValue = "Some Other Value"; // work fine
         }
    }
}

that continues to make no sense.

there's no reason you should be using a switch statement in that code.  use:

protected function udpDataHandler(event.DatagramSocketDataEvent):void{

var o:Object = event.data.readObject();

if(o.command){

NewValue=o.command;

} else {

NewValue=0;

}

}

// and i have no idea what you're doing in timeHandler but myArray must be a very poor choice of names because that can't be an array.

Haha probably just a bind or invalid type issue.

You made NewValue an object. That means you need to assign a property to it. If you want to read a string, simply convert NewValue to a String instead of an object.

Do one of these two things:

1) Add a property to NewValue if you keep it an object, e.g.

NewValue.value = o.command;

2) Change NewValue to a String

// at the top of the class

public var NewValue:String;

// assignment, just how you have it now

NewValue = o.command;

Besides that, you really need to stop adding the switch in there. That switch is absolutely pointless. There is no difference between that switch and this:

if (true) {

     messageArea.appendText(o.command);

     NewValue = o.command;

}

The code above is pointless. It will happen 100% of the time. So ditch the switch. Just make it:

try

{

     var o:Object = event.data.readUTFBytes(event.data.bytesAvailable);

     if (o.command)

     {

          messageArea.appendText(o.command);

          NewValue = o.command;

     }

     else

     {

          NewValue = ""; // set to empty string (if you change NewValues type to String)

     }

}

catch (e)

{

     event.data.position = 0;

     messageArea.appendText(event.data.readUTFBytes(event.data.bytesAvaila ble));

}

You can use a switch, but if you only provide a default it will do that every single time. That's why it's 100% useless. You need to provide cases for the switch statement for it to do different things based on what comes in.

e.g.

switch(o.command)

{

     case "": // contains nothing

          event.data.position = 0;

          messageArea.appendText(event.data.readUTFBytes(event.data.bytesAvaila ble)); // just write out whatever the bytes were (this is kinda useless too)

          break;

     default: // it contains SOMETHING, so use it, but containing nothing was handled above

          messageArea.appendText(o.command);

          NewValue = o.command; // assuming this is type String

          break;

}

Haha yep. Just get that default-only switch statement out of there . It's not doing anything at all.

Glad you got it fixed.

Sorry I don't know the chart components but that should be kept in another thread anyhow. That's more of a flex question.