FEATURE POLL. PowerLanguage

Questions about MultiCharts and user contributed studies.

FEATURE POLL. PowerLanguage

When ‘begin’ is entered in PLEditor, automaticall insert a matching ‘end’
8
21%
I_OpenEquity and I_ClosedEquity fucntions
20
51%
TL_New_BN(StartBarNumber, StartValue, EndBarNumber, EndValue)
11
28%
 
Total votes: 39

User avatar
Andrew Kirillov
Posts: 1589
Joined: 28 Jul 2005
Has thanked: 2 times
Been thanked: 31 times
Contact:

FEATURE POLL. PowerLanguage

Postby Andrew Kirillov » 26 Mar 2008

FEATURE POLL. PowerLanguage
Last edited by Andrew Kirillov on 19 Jun 2008, edited 1 time in total.

drwar
Posts: 218
Joined: 31 Jul 2005

Postby drwar » 26 Mar 2008

I hope the selection TL_New included Text_New in this Poll

User avatar
Geoff
Posts: 198
Joined: 18 Apr 2007
Has thanked: 15 times
Been thanked: 4 times

Postby Geoff » 08 Apr 2008

Add ability to plot text x number of bars back. Text_New uses BarDate, BarTime which makes it difficult to use on tick and volume charts.

User avatar
RobotMan
Posts: 375
Joined: 12 Jul 2006
Location: Los Altos, California, USA
Has thanked: 31 times
Been thanked: 13 times
Contact:

Postby RobotMan » 08 Apr 2008

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

User avatar
MC_Prog
Posts: 330
Joined: 28 Feb 2007
Has thanked: 64 times
Been thanked: 35 times

Postby MC_Prog » 09 Apr 2008

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.

User avatar
danilo
Posts: 170
Joined: 02 Jan 2007
Location: Italy
Has thanked: 4 times
Been thanked: 9 times

Postby danilo » 23 Apr 2008

Andrew,

Since the strategies are getting always more complex, could be possible to add to PowerLanguage the capability to use "Macros" or "Inline" functions inside a signal to embeed Buy/Sell stetements ?

Regards,
Danilo

User avatar
Marina Pashkova
Posts: 2758
Joined: 27 Jul 2007

Postby Marina Pashkova » 14 May 2008

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.
Hi MC_Prog,

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.

User avatar
Marina Pashkova
Posts: 2758
Joined: 27 Jul 2007

Postby Marina Pashkova » 14 May 2008

Andrew,

Since the strategies are getting always more complex, could be possible to add to PowerLanguage the capability to use "Macros" or "Inline" functions inside a signal to embeed Buy/Sell stetements ?

Regards,
Danilo
Hi Danilo,

It'll be done in future MC versions.

aljafp
Posts: 184
Joined: 28 Oct 2005
Been thanked: 1 time

Postby aljafp » 14 Jun 2008

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.


Return to “MultiCharts”