Daedalus
01-10-2007, 01:06 PM
When I compile my app to test it (either by running or debuging it) I sometimes get this message in flash>
ArgumentError: Error #1063: Argument count mismatch on Box$iinit(). Expected 2, got 0.
However it has nothing to do with my code because I have checked everything out by debuging and all is fine. As I just mentioned, It only does it about half the time.
I could compile it and it would generate the message above and then compile it again (making no code changes) and it will work fine.
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"
creationComplete="init()">
<mx:Script>
import mx.controls.*;
private function init():void
{
//Settings.loadSettings();
var st:stageBox = new stageBox();
this.rawChildren.addChild(st);
var gd:GradientStyleOb = new GradientStyleOb(GradientType.LINEAR, [0xFF0000, 0x0000FF], [100, 100], [0, 255]);
var ln:lineStyleOb = new lineStyleOb(1);
var tst:Box = new Box(200,200, "M:C", null, ln, gd);
st.addChild(tst);
var ts:Box = new Box(50,50, "150:150", null, ln, gd);
tst.addChild(ts);
}
</mx:Script>
</mx:Application>
Other times I simply get no errors but nothing happens, in IE all I get is the blank blue flex screen with no components appearing. If I compile again it will suddently work fine!
With these two issues above if I debug AND put a breakpoint in one of my lines of code in my init function it will work fine everytime, but as soon as I debug without breakpoints or just run it normally I get this funny behaviour.
Another problem that sometimes happens is that I get the connect to debugger window appear in IE when I run the app. This is the window that prompts you to select where the debugger is running either on localhost or another machine. Even If I select local host it still wont connect to the debugger.
These problems used to happen only now and again when I upgraded but now they are happening 90% of the time making running and debuging flex/actionscript 3 apps almost impossible.
Restarting flex has no effect either.
I thought it might be IE but I tried it on firefox and Opera and I get the same thing.
Anyone else had these problems?
ArgumentError: Error #1063: Argument count mismatch on Box$iinit(). Expected 2, got 0.
However it has nothing to do with my code because I have checked everything out by debuging and all is fine. As I just mentioned, It only does it about half the time.
I could compile it and it would generate the message above and then compile it again (making no code changes) and it will work fine.
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"
creationComplete="init()">
<mx:Script>
import mx.controls.*;
private function init():void
{
//Settings.loadSettings();
var st:stageBox = new stageBox();
this.rawChildren.addChild(st);
var gd:GradientStyleOb = new GradientStyleOb(GradientType.LINEAR, [0xFF0000, 0x0000FF], [100, 100], [0, 255]);
var ln:lineStyleOb = new lineStyleOb(1);
var tst:Box = new Box(200,200, "M:C", null, ln, gd);
st.addChild(tst);
var ts:Box = new Box(50,50, "150:150", null, ln, gd);
tst.addChild(ts);
}
</mx:Script>
</mx:Application>
Other times I simply get no errors but nothing happens, in IE all I get is the blank blue flex screen with no components appearing. If I compile again it will suddently work fine!
With these two issues above if I debug AND put a breakpoint in one of my lines of code in my init function it will work fine everytime, but as soon as I debug without breakpoints or just run it normally I get this funny behaviour.
Another problem that sometimes happens is that I get the connect to debugger window appear in IE when I run the app. This is the window that prompts you to select where the debugger is running either on localhost or another machine. Even If I select local host it still wont connect to the debugger.
These problems used to happen only now and again when I upgraded but now they are happening 90% of the time making running and debuging flex/actionscript 3 apps almost impossible.
Restarting flex has no effect either.
I thought it might be IE but I tried it on firefox and Opera and I get the same thing.
Anyone else had these problems?