Hi Marina,
I am looking forward to the 5.3 beta and gold release. It looks like you will have an almost perfect piece of trading software by then.
I have only one additional request.
Esignal does some annoying things with their equities data. There are two data fields to get the last trade:
1. "Last Trade Price"
2. "Last/Extended Hours Last"
Currently Multicharts uses the first option to plot charts. After the cash markets close and new trades are coming through Multicharts will not chart new data.
If Multicharts uses the second data option (Last/Extended Hours Last) then esignal will always give the last trade price and after hours charts will plot.
At this time Multicharts cannot plot after hour equities with Esignal Data.
After Hours Equities Data with Esignal
-
- Posts: 261
- Joined: 28 Feb 2008
- Has thanked: 2 times
- Been thanked: 1 time
-
- Posts: 261
- Joined: 28 Feb 2008
- Has thanked: 2 times
- Been thanked: 1 time
- Marina Pashkova
- Posts: 2758
- Joined: 27 Jul 2007
- Marina Pashkova
- Posts: 2758
- Joined: 27 Jul 2007
Hi flipflopper,
MultiCharts uses whatever fields are available through eSignal's API.
As for extended vs regular hours values, could you please give us a symbol that can be used in our tests to see the difference? Also, could you please tell us where the field shown in your screenshot can be found in eSignal's platform?
Thank you.
MultiCharts uses whatever fields are available through eSignal's API.
As for extended vs regular hours values, could you please give us a symbol that can be used in our tests to see the difference? Also, could you please tell us where the field shown in your screenshot can be found in eSignal's platform?
Thank you.
-
- Posts: 261
- Joined: 28 Feb 2008
- Has thanked: 2 times
- Been thanked: 1 time
- Marina Pashkova
- Posts: 2758
- Joined: 27 Jul 2007
Hi flipflopper,
Thank you for the additional information.
Our engineers will first check if the Extended Hours Last field can be received through eSignal's API. The thing is that what is available in eSignal's platform itself might not be available through their API. We need to find out if this is the case or not. If the Extended Hours Last is available through the API we will see if we can incorporate it into our connection to eSignal.
Regards.
Thank you for the additional information.
Our engineers will first check if the Extended Hours Last field can be received through eSignal's API. The thing is that what is available in eSignal's platform itself might not be available through their API. We need to find out if this is the case or not. If the Extended Hours Last is available through the API we will see if we can incorporate it into our connection to eSignal.
Regards.
-
- Posts: 261
- Joined: 28 Feb 2008
- Has thanked: 2 times
- Been thanked: 1 time
- Marina Pashkova
- Posts: 2758
- Joined: 27 Jul 2007
Hi flipflopper,
All the engineers are working on preparing beta 3 to be released. Therefore, we have not been able to find out whether eSignal allows addressing those after hours values via their API or not.
As soon as the beta is released (this week), they will study the question to give you an answer.
Regards.
All the engineers are working on preparing beta 3 to be released. Therefore, we have not been able to find out whether eSignal allows addressing those after hours values via their API or not.
As soon as the beta is released (this week), they will study the question to give you an answer.
Regards.
-
- Posts: 261
- Joined: 28 Feb 2008
- Has thanked: 2 times
- Been thanked: 1 time
-
- Posts: 261
- Joined: 28 Feb 2008
- Has thanked: 2 times
- Been thanked: 1 time
- Andrew Kirillov
- Posts: 1589
- Joined: 28 Jul 2005
- Has thanked: 2 times
- Been thanked: 31 times
- Contact:
We took a look at this issue. We were under impression that it is easy to set a flag to receive extended hours last, but is it not easy. We will have to use different methods to get data. So it is a small project, rather than a minor change.
The most important issue is that we are concerned that we will damage the previous debugged functionality.
Since we are targeting MC 5.0 release this month we decided to add this improvement in 5.1. It will be safer.
Thank you for understanding.
The most important issue is that we are concerned that we will damage the previous debugged functionality.
Since we are targeting MC 5.0 release this month we decided to add this improvement in 5.1. It will be safer.
Thank you for understanding.
-
- Posts: 261
- Joined: 28 Feb 2008
- Has thanked: 2 times
- Been thanked: 1 time
-
- Posts: 261
- Joined: 28 Feb 2008
- Has thanked: 2 times
- Been thanked: 1 time
- Andrew Kirillov
- Posts: 1589
- Joined: 28 Jul 2005
- Has thanked: 2 times
- Been thanked: 31 times
- Contact:
-
- Posts: 261
- Joined: 28 Feb 2008
- Has thanked: 2 times
- Been thanked: 1 time