Home› AMX Forum› NetLinx Studio
Options

Netlinx studio 2.5 wierd error

Duncan EllisDuncan Ellis Code Junkie
in NetLinx Studio
I was just starting some new code, and started to add a new DEFINE_CALL and Netlinx Studio froze and a popup box appeared with the message 'the parameter is incorrect' and wouldn't go away. The only option was to close studio. Anyone else encountered this????
· Share on FacebookShare on Twitter

Comments

  • DHawthorneDHawthorne Junior Member
    Not me; I've put maybe 8 hours in on the new version, haven't noticied anything unusual.
    · Share on FacebookShare on Twitter
  • Marc ScheibeinMarc Scheibein Junior Member
    Duncan Ellis wrote:
    I was just starting some new code, and started to add a new DEFINE_CALL and Netlinx Studio froze and a popup box appeared with the message 'the parameter is incorrect' and wouldn't go away. The only option was to close studio. Anyone else encountered this????

    I've got the same some minutes ago with creating a Function.... unfortunately I can't reproduce for reporting....
    · Share on FacebookShare on Twitter
  • Marc ScheibeinMarc Scheibein Junior Member
    Marc Scheibein wrote:
    I've got the same some minutes ago with creating a Function.... unfortunately I can't reproduce for reporting....

    It IS reproducable..... doesn't matter if it is a new or existing code file.

    Just try to type 
    DEFINE_FUNCTION ()
    and it will crash.... Upper/lower case doesn't matter. It crashes just when typing the '(' directly after the DEFINE_FUNCTION keyword without a function name.

    But I can't reproduce with DEFINE_CALL.
    · Share on FacebookShare on Twitter
  • ldeblank@jnv.nlldeblank@jnv.nl Junior Member
    error

    Had the same problem.
    It seems the problems occurs when you add a new function (or Call). As you type DEFINE_FUNCTION and the help function is activated netlinx studio hangs.
    A work around for me is to copy an existing function (CTRL+C) and Paste it (CTRL+V) and then change whatever you want.
    Good Luck
    · Share on FacebookShare on Twitter
  • Marc ScheibeinMarc Scheibein Junior Member
    ldeblank@jnv.nl wrote:
    Had the same problem.
    It seems the problems occurs when you add a new function (or Call). As you type DEFINE_FUNCTION and the help function is activated netlinx studio hangs.
    A work around for me is to copy an existing function (CTRL+C) and Paste it (CTRL+V) and then change whatever you want.
    Good Luck

    Another was is first to write your function name and then adding the DEFINE_FUNCTION Keyword... (I think there are a LOT of ways to work around ;))
    · Share on FacebookShare on Twitter
  • ryanwwryanww Junior Member
    I also had the error for the Define_Call problem just erroring out with the message above.

    Ryan
    · Share on FacebookShare on Twitter
  • ryanwwryanww Junior Member
    Found a work around. I already had a define call in the code, so I just coppied and pasted it and changed everything else but the define_call and it worked.

    Ryan
    · Share on FacebookShare on Twitter
  • DHawthorneDHawthorne Junior Member
    I just had an interesting variation on this one. I absentmindedly started defining a CALL without any of the above mentioned workarounds, and got the endless error message crash. OK, so I three-finger-saluted it, and re-opened Studio. As my wonderful luck would have it, the code had just auto saved, so there was a single line with DEFINE_CALL in it, and nothing else. I have workspace restoration turned on, so Studio attempted to open it on a re-start, and to my horror, I got the dreaded Bad Parameter dialog. Only this time it wasn't endless ... I could click it off. But then, that particular piece of source code now appeared in studio on a tab with no name at all, just the AXS icon. And the file appeared without any highlighting at all ... matter of fact, none of the editor settings applied either. I have my editor set with a black background, and contrasting text colors, but this file appeared with a white background, and black text ... my terminal screen settings. So I closed it (I think), opened the file in a text editor, added my CALL name and parameters, and reopened it in Studio. All was well after that, but curiously, I am reasonably sure I had closed the phantom file tab ... yet it opened up again when I opened the fixed code file. There were now two variants in the worksapce, the no-name, terminal-screen looking one, and the corrected file. I closed the bad one again, and it did not come back after that.
    · Share on FacebookShare on Twitter
  • bmattiuzbmattiuz Junior Member
    Modules?

    I just had that same problem, but it only happens when i'm in a module file.
    · Share on FacebookShare on Twitter
  • ColzieColzie Senior Member
    Projects on a network drive cause problems

    I am having a slightly different problem with 2.5. I upgraded to 2.5 and everything went fine. I worked on some projects in the office, then at a client's place. Now (Saturday) I'm at home and can't open ANY axi or axs file - I get "The parameter is incorrect".

    I tested creating a new workspace and master source file. The new source file comes up, but the colors are weird (perhaps default?). If I try to save the file, I get an error.

    The cause of these problems is my projects folder is a network drive that is available offline. When I copy a project to a physical drive, it opens fine (though the colors are still nasty), or if I create a project on a physical drive, it works fine. This will be a huge hassle if I have to copy each project to a local drive when working away from the office.
    · Share on FacebookShare on Twitter
Sign In or Register to comment.