Announcement

Collapse
No announcement yet.

t&s history

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

  • #31
    windows 2000 not working - XPPro is

    Our app as well as the esigvbticks.zip app posted quite a ways below in this thread by George works great with Windows XPPro, but not on our Windows2000 machine. All seems up to date.

    The app seems to connect to esignal and even gets notification that the history is done. No errors, it just seems that the esignal_OnTimeSalesChanged event never triggers. Same on our app both in vb.net.

    Does seem that some others have indicated this situation where something works on XPPro, but not Windows2000 regarding the DesktopAPI, but not sure what was done about it.

    Any suggestions of what to look for? Like I say, many things seem to work with the interface, but not the esignal_OnTimeSalesChanged.

    Comment


    • #32
      more on Win2000 vs. XP

      Put in some more error code checking and (still working with George's app posted below) here's something that is happening in the OnTimeSalesChanged event in windows2000 that is not happening in XP.

      Dim tick as IESignal.TimeSalesData

      'if we put the next statement in a Try..End Try routine

      Try
      tick=esignal.GetTimeSalesBar(lHandle,0)
      Catch ex as Exception
      Msgbox(ex.message)
      End Try

      We get "Invalid access to memory location". Without the "Try" the sub just stops at that point in the code.

      Comment


      • #33
        I wonder what would happen using absolute indexing mode (i.e. where zero is the first tick in time instead of the last (i.e. most recent) tick)? Just a random curiousity which probably wouldn't change anything.

        Comment


        • #34
          hmmm

          George (or anyone that can help)

          Thanks for your suggestion. That does make some sense. Decided to see if we could determin if there were any bars available for could find that out without an error.

          Remarked all the code on the IsTimeSalesChanged event so it wouldn't cause a problem.

          Still do get the history is completed notification from your app.

          Then just added a button to check for GetNumBars and we get 0.

          Button click does this:

          Dim tick as IESignal.TimeSalesData
          Dim it as long
          it = esignal.GetNumBars(tshandle)
          msgbox(it)

          Did put it in a "Try..Catch..End" routine, but no error... Just 0 bars for the count. Hmmm...

          Shouldn't there be something there even if the markets are dead?

          The filter is requesting a day (one day) of history and we are not requesting real time bars.

          Hmmm... there should be some bars. Even if the markets are not open. There should be bars. I guess I will check this out on an XP machine. Then back to the Win2000.

          No error in this case, just 0 for bars.

          Comment


          • #35
            correction

            ok, so i needed to do esignal.GetNumTimeSalesBars(tshandle)

            not esignal.GetNumBars(tshandle)

            Now I'm getting bars on win2000 fine. On to why not a particular bar with that memory error jazz.

            Comment


            • #36
              more on Win2000 vs. XP

              Stumped. Using VB.net and retrieving t&s. This small bit of code works fine on XPPro it seems, but when we try it on a Windows2000 machine we get an exception trying to retrieve "tick = esignal.GetTimeSalesBar(tsHandle, 0)" or any index for the .GetTimeSalesBar.

              Using the "esignal.GetNumTimeSalesBars(tsHandle)" returns the number of sales bars even as they grow so it seems the request to the desktop api is successful and we can get a count of the bars indicating they are there. It even returns true to the is time and sales history ready jazz.

              The exception when executing "tick = esignal.GetTimeSalesBar(tsHandle, 0)" is:

              "System.Runtime.InteropServices.COMException (0x800703E6): Invalid access to memory location. at IESignal.HooksClass.get_GetTimeSalesBar(Int32 lHandle, Int32 lbarIndex) at [the name of our sample app.Form1.Button2_Click(Object sender, EventArgs e) in [the path of our sample app]\Form1.vb:line 153.

              The ex.source = Interop.IESignal

              Here's the more complete, but yet quite brief code sniplets:

              Public Class Form1
              Inherits System.Windows.Forms.Form

              Public WithEvents esignal As IESignal.Hooks
              Dim tsHandle As Integer

              ....

              esignal = New IESignal.Hooks
              esignal.SetApplication("usernamehere")

              Dim filter As IESignal.TimeSalesFilter

              filter = New IESignal.TimeSalesFilter
              filter.bFilterPrice = 0
              filter.bFilterQuoteExchanges = 0
              filter.bFilterTradeExchanges = 0
              filter.bFilterVolume = 0
              filter.bQuotes = 1
              filter.bTrades = 1
              filter.lNumDays = 1
              filter.sSymbol = "es u4"
              tsHandle = esignal.RequestTimeSales(filter)

              ...
              'this will work fine

              Dim lt As Long = esignal.GetNumTimeSalesBars(tsHandle)
              MsgBox(lt.ToString)

              'this will throw the exception
              Dim tick As IESignal.TimeSalesData
              tick = esignal.GetTimeSalesBar(tsHandle, 0)

              'tried with different index values and setting the indexing to absolute and George suggested. What do you think is going on?

              Comment


              • #37
                getting t&s bar w/Win2000 & vb.net

                This is still an urgent matter for us (see previous postings in this thread). Just wondering if we might be anticipating a response from esignal engineers or ???.

                Comment


                • #38
                  Test app

                  This is the simplest test app I could think of for getting Time & Sales data, please try this out and see if it works for you.

                  Also, are you building these on Windows 2000, or just copying them over? It shouldn't make a difference, but I forget if building an interop application installs some assemblies or not.

                  Simon.
                  Attached Files
                  Simon Thornington
                  eSignal Developer

                  Comment


                  • #39
                    We are aware of some problems that have surfaced in a Windows 2000 environment. We are working on getting our developer set up with a W2K environment to dig into the problems, but these may take a few weeks to get to the bottom of.

                    Comment


                    • #40
                      last word, for a bit, it seems

                      Simon, thanks for the "most simple code". There were some "Imports" that we (and George) had not included in our code and thought that might make a difference, but it didn't.

                      Also, we did initially just install the app (which was developed in XP environment) on a Win2000 machine. Then we installed Visual Studio.net on a Win2000 machine and ran the code there, then we actually wrote the code on the Win2000 machine and ran.

                      Looks like's Robi's input is the case unless someone comes up with something creative.

                      We're converting the first user of this app to XPPro. Not sure how we handle additional customers who have Win2000 and we do have at least two with esignal that are interested (and have win2000).

                      Maybe we will just have such a great idea that end users will be anxious to convert to XP which would be good all around or maybe y'all will get the DesktopAPI/Win2000 thingy addressed.

                      Thanks for your responses. We really just need to know what we are dealing with and want to make sure we are not just doing something stupid or uninformed.

                      Thanks again.

                      Curtis Gaylord

                      Comment

                      Working...
                      X