Home› AMX User Forum› NetLinx Studio

NetLinx Studio v3.4.908

nicholasjamesnicholasjames Posts: 154
in NetLinx Studio
For those who may not yet be privy, there's a new version of NetLinx Studio: 
[B]NetLinx Studio v3.4.908[/B]

FEATURE - Support for the new TP5 Touch Panel Files (G5 Panels). Ability to add 
TP5 files to the NetLinx Studio Workspace and the ability to transfer to the 
new panels.

FEATURE: Support for the new Driver Design Module files (.xdd). Ability to add
XDD files to the NetLinx Studio Workspace and the ability to transfer to the 
masters controllers.

BUG FIX - Corrected the problem of the NetLinx Compiler not reporting the correct 
file name when displaying the #WARN compiler directive within NetLinx Studio when 
the #WARN directive was located in an include file (.AXI). The NetLinx Compiler
Version is now [2.5.2.300].

BUG FIX - Reactivated the "Check Port Status" menu item within the Online Tree.

BUG FIX - Corrected the problem of exporting AXS/AXI files to an AXW file when
the user selected to "Exclude" these files from the export.

BUG FIX - Resolved the problem of transferring files to Axcent controllers.

I am happy about the #WARN fix, but sad that it breaks again if you have an include in an include...

Have you noticed any additional changes/bugs with this release?

Comments

  • jjamesjjames Posts: 2,908
    My favorite -- the ability to pull the TKN from the master. While I know you could do it in v3 firmware quite easily with FTP, it was broken (ahem, fixed) in v4 firmware.
  • nicholasjamesnicholasjames Posts: 154
    jjames wrote: »
    My favorite -- the ability to pull the TKN from the master. While I know you could do it in v3 firmware quite easily with FTP, it was broken (ahem, fixed) in v4 firmware.

    Oh great! I didn't notice that. That's definitely going to make life easier when the code is mission-critical.
  • Jim DonachiueJim Donachiue Posts: 82
    Before I install this;
    has anyone had any problems that would cause issues with existing code?
  • ericmedleyericmedley Posts: 4,177
    I did notice that VERSION must now be a keyword or name of a data structure now. I had a module that used a constant named VERSION and upon compile with the new NS threw an error. I changed the name of the constant to. VERSION_REQUEST and all was well.

    Reminded me of the days of updating AXCESS code where everyone used the word SWITCH for a device and/or variable name for a audio/video switcher.
  • nicholasjamesnicholasjames Posts: 154
    ericmedley wrote: »
    I did notice that VERSION must now be a keyword or name of a data structure now. I had a module that used a constant named VERSION and upon compile with the new NS threw an error. I changed the name of the constant to. VERSION_REQUEST and all was well.

    Reminded me of the days of updating AXCESS code where everyone used the word SWITCH for a device and/or variable name for a audio/video switcher.

    No, this must be a bug. If VERSION is defined as a CONSTANT I get the error "C10206: STRUCTURE type [CHAR] already defined". However define it as a variable and it compiles fine.
  • nicholasjamesnicholasjames Posts: 154
    Just noticed two new registry entries under "KIT Files": "HttpServerPort" and "HttpServerSelected". Anybody know if the URL updating of touchpanels (described in this post) is also coming to firmware? Or perhaps enter a URL (such as amx.com/firmware) to get a list of the most current firmware?

    Nevermind. Just noticed the option and help text box in the Firmware Transfer Preferences.
  • ericmedleyericmedley Posts: 4,177
    nicholasjames wrote: »
    No, this must be a bug. If VERSION is defined as a CONSTANT I get the error "C10206: STRUCTURE type [CHAR] already defined". However define it as a variable and it compiles fine.

    Perhapso. Either way it broke my code and either way it needed fixing. :)

    To be honest it surprises me that stuff like this doesn't happen more often. There are several under-the-hood variables and structures in Netlinx that could horse a persons code up.
  • jjamesjjames Posts: 2,908
    FYI - I tried using VERSION as a constant in build 600 of studio and had the same error - so it's not a compiler issue as the compiler changed only in 908. Build 525 (release) and 600 (TN 999) had the same compiler that hadn't been touched in years.
  • nicholasjamesnicholasjames Posts: 154
    jjames wrote: »
    FYI - I tried using VERSION as a constant in build 600 of studio and had the same error - so it's not a compiler issue as the compiler changed only in 908. Build 525 (release) and 600 (TN 999) had the same compiler that hadn't been touched in years.

    Ah, gotcha. So Eric, I guess you haven't been using the hotfix version.
Sign In or Register to comment.