Announcement

Collapse
No announcement yet.

EFS Study not working correctly in 10.5

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • EFS Study not working correctly in 10.5

    I upgraded to 10.5 and an EFS Study I wrote to do automated trading thru DLL calls has stopped working correctly. It still runs and some of the function calls still work.

    I rolled the installation back to 10.4 and the study works correctly.

    Before I start to debug the problem, I wanted to see if anyone else was having a related problem with 10.5 and EFS.

    Thanks,
    Greg

  • #2
    I have not upgraded yet to 10.5. Maybe they changed something with dll handling?

    I'm sure a technician from esignal will reply to this one.
    Brad Matheny
    eSignal Solution Provider since 2000

    Comment


    • #3
      Hello Greg,

      We have not received any other reports of the problem you're describing. We would like to investigate this further. Can you provide more specific details as to the functions that have stopped working? If you can isolate the issues and put together a basic sample dll that can be used to reproduce the problem it would be very helpful.

      Thanks,
      Jason K.
      Project Manager
      eSignal - an Interactive Data company

      EFS KnowledgeBase
      JavaScript for EFS Video Series
      EFS Beginner Tutorial Series
      EFS Glossary
      Custom EFS Development Policy

      New User Orientation

      Comment


      • #4
        Hi Jason,
        I finally figured out what the problem was. In version 10.4, if a variable was left out of a DLL call, the variable defaulted to 0. In 10.5 it defaults to something else (I'm not sure what). The solution was to explicitly include the variable in the DLL call.

        Original code (worked in 10.4, but not 10.5)
        d.addFunction("ProcessMsgs",DLL.STRING, DLL.CDECL, "?fProcessMessages@@YAPBDH@Z");

        Revised code (works in 10.5)
        d.addFunction("ProcessMsgs",DLL.STRING, DLL.CDECL, "?fProcessMessages@@YAPBDH@Z", DLL.INT);

        Greg

        Comment


        • #5
          Hello Greg,

          Thanks for the update. I'll pass this along to our engineering team to investigate further.
          Jason K.
          Project Manager
          eSignal - an Interactive Data company

          EFS KnowledgeBase
          JavaScript for EFS Video Series
          EFS Beginner Tutorial Series
          EFS Glossary
          Custom EFS Development Policy

          New User Orientation

          Comment


          • #6
            Hello Greg,

            Our engineers have investigated and confirmed that there has not been any intentional changes to the behavior of this function. However, we did add some error handling/tracing routines that may be changing the stack that is causing this problem. We can't undo those changes, however. You will need to specify the parameter types going forward. We'll update the documentation and make the parameter type a required input for future users.
            Jason K.
            Project Manager
            eSignal - an Interactive Data company

            EFS KnowledgeBase
            JavaScript for EFS Video Series
            EFS Beginner Tutorial Series
            EFS Glossary
            Custom EFS Development Policy

            New User Orientation

            Comment

            Working...
            X