FEATURE POLL. PowerLanguage
- Andrew Kirillov
- Posts: 1589
- Joined: 28 Jul 2005
- Has thanked: 2 times
- Been thanked: 31 times
- Contact:
FEATURE POLL. PowerLanguage
FEATURE POLL. PowerLanguage
Last edited by Andrew Kirillov on 19 Jun 2008, edited 1 time in total.
- RobotMan
- Posts: 375
- Joined: 12 Jul 2006
- Location: Los Altos, California, USA
- Has thanked: 31 times
- Been thanked: 13 times
- Contact:
Hi Geoff and Jerry,
I agree and second your suggestion.
Anyone that has done any programming for intra-day studies and indicators has had to deal with the outmoded way that TS deals with bars. It presumes that EVERYONE uses time based charts and that EVERYONE uses time intervals longer than 59 seconds. I have always wished that all trend lines, text, etc was barnumber based. Even now, I always use time_s just because of this, but it would be so much better if I could use barnumber.
Thank Goodness for Multicharts, but I think we can still do better by instituting barnumber based TL and Text.
Bob Perry
Los Altos, CA
I agree and second your suggestion.
Anyone that has done any programming for intra-day studies and indicators has had to deal with the outmoded way that TS deals with bars. It presumes that EVERYONE uses time based charts and that EVERYONE uses time intervals longer than 59 seconds. I have always wished that all trend lines, text, etc was barnumber based. Even now, I always use time_s just because of this, but it would be so much better if I could use barnumber.
Thank Goodness for Multicharts, but I think we can still do better by instituting barnumber based TL and Text.
Bob Perry
Los Altos, CA
IMO, all the I_ functions are critical must-haves.
A very large percentage of 3rd party products for TS use these functions.
Not having them available means that the equivalent product for MC either is a crippled version, or is simply not released at all because the developer doesn't want to release a half-baked implementation.
Please give a high priority to building the I_ functions into MC.
A very large percentage of 3rd party products for TS use these functions.
Not having them available means that the equivalent product for MC either is a crippled version, or is simply not released at all because the developer doesn't want to release a half-baked implementation.
Please give a high priority to building the I_ functions into MC.
- Marina Pashkova
- Posts: 2758
- Joined: 27 Jul 2007
Hi MC_Prog,IMO, all the I_ functions are critical must-haves.
A very large percentage of 3rd party products for TS use these functions.
Not having them available means that the equivalent product for MC either is a crippled version, or is simply not released at all because the developer doesn't want to release a half-baked implementation.
Please give a high priority to building the I_ functions into MC.
You are absolutely right and this feature has been assigned high priority. The thing is that we already have a number of high priority projects going on. As soon as they are implemented we'll start working on I_functions. June - July is a rough estimate.
Regards.
- Marina Pashkova
- Posts: 2758
- Joined: 27 Jul 2007
Currently with powerlanguage we can only "Buy next bar at market",
i.e when a tick is processed by MC and the strategy determines that a buy condition is satisfied, the order will only be executed when the NEXT TICK enters MC.
When really, what the user wants is to buy immediately ... this delay is unnecessary.
i.e when a tick is processed by MC and the strategy determines that a buy condition is satisfied, the order will only be executed when the NEXT TICK enters MC.
When really, what the user wants is to buy immediately ... this delay is unnecessary.