ObjectCreate("LabelBox1", OBJ_LABEL, 0, 0, 0); ObjectSetText("LabelBox1","g",300,"Webdings",DarkGray); ObjectSet("LabelBox1", OBJPROP_XDISTANCE, 90); ObjectSet("LabelBox1", OBJPROP_YDISTANCE, 25); ObjectSet("LabelBox1",OBJPROP_BACK,0);
   ObjectCreate("LabelBox2", OBJ_LABEL, 0, 0, 0); ObjectSetText("LabelBox2","g",300,"Webdings",White); ObjectSet("LabelBox2", OBJPROP_XDISTANCE, 86); ObjectSet("LabelBox2", OBJPROP_YDISTANCE, 21); ObjectSet("LabelBox2",OBJPROP_BACK,0);

youcrazykids wrote:Hi all

Although nothing startling, I've found a way of displaying comments and screen messages, without them being obscured by bars on the chart.

To do this, in the init() function, I add two text labels to the chart, at coordinates 0,0. The Webdings character set contains a solid block, which you can scale up to 150pts, to create a "box". So, a couple of these stacked vertically, then coloured black, does the trick. The comment text sits atop these, and they both stay fixed relative to the window, not the scrolling chart.

Here's the code, and a screenshot. Feel free to adopt/adapt/ridicule it as you wish

Code: Select all

ObjectCreate("LabelBox1", OBJ_LABEL, 0, 0, 0); ObjectSetText("LabelBox1","g",150,"Webdings",Black); ObjectSet("LabelBox1", OBJPROP_XDISTANCE, 0); ObjectSet("LabelBox1", OBJPROP_YDISTANCE, 13); ObjectSet("LabelBox1",OBJPROP_BACK,0);
ObjectCreate("LabelBox2", OBJ_LABEL, 0, 0, 0); ObjectSetText("LabelBox2","g",150,"Webdings",Black); ObjectSet("LabelBox2", OBJPROP_XDISTANCE, 0); ObjectSet("LabelBox2", OBJPROP_YDISTANCE, 213); ObjectSet("LabelBox2",OBJPROP_BACK,0);
Comment("","\ntext text text text text text text text text text");

Example.JPG

Cheers

youcrazykids[/size]

gaheitman wrote:I thought this was way cool too, and while I'm waiting for the US Session to roll around I decided to play with your idea a bit.

I changed the font to 300 for both of them. I use a white background with my charts, so I changed the color of the first one to white and the second to dark grey. I then offset the first one to line up with the beginning of the comment display and the second to be slightly offset from the first. The final effect is what looks like a floating window with a shadow. I know, I know, time well spent.

The code:

Code: Select all

   ObjectCreate("LabelBox1", OBJ_LABEL, 0, 0, 0); ObjectSetText("LabelBox1","g",300,"Webdings",DarkGray); ObjectSet("LabelBox1", OBJPROP_XDISTANCE, 90); ObjectSet("LabelBox1", OBJPROP_YDISTANCE, 25); ObjectSet("LabelBox1",OBJPROP_BACK,0);
   ObjectCreate("LabelBox2", OBJ_LABEL, 0, 0, 0); ObjectSetText("LabelBox2","g",300,"Webdings",White); ObjectSet("LabelBox2", OBJPROP_XDISTANCE, 86); ObjectSet("LabelBox2", OBJPROP_YDISTANCE, 21); ObjectSet("LabelBox2",OBJPROP_BACK,0);

The pretty picture:

pic_04 2011-11-30 05.42.gif

Enjoy! ;>

• Naive trader sends a trade.
  Platform freezes up before there is time to send the modification of the trade that adds a sl/tp.
  Said platform freeze can be encouraged/simulated by all sorts of thingies that are 'out of control of the broker. Please be assured that we continue to develop our services to the benefit of our valued clients '.

• We can send trades without stops
  The stops we try to send as a second stage, will not be accepted. Ok, so they all offer that bloody silly order form that allow us to input stops, but it seems there is not guarantee that the stop modifications will actually happen

SteveHopwood wrote:Latest update in post 1.

For those of a delicate disposition, here is the sanitised rationale:
It appears that the markets can sometimes be moving so quickly that ECN brokers will be unable to allow modifications of trades that update stop losses and take profits. I have added code to CountOpenTrades() that will detect when this happens, and further call functions that will replace the missing tp/sl.


Now, here is what I really mean. Do not read on if bad language offends you.

Only a total tit fails to recognise that some bastard criminals have rabidly adopted ECN in the hope that this will happen:

• Naive trader sends a trade.
  Platform freezes up before there is time to send the modification of the trade that adds a sl/tp.
  Said platform freeze can be encouraged/simulated by all sorts of thingies that are 'out of control of the broker. Please be assured that we continue to develop our services to the benefit of our valued clients '.

Total shits.

So, these mindless, turd-brained (and I use the term 'brained' with reservation), manipulative fucking bastards are forcing those of us daft enough to play their game to accept that:

• We can send trades without stops
  The stops we try to send as a second stage, will not be accepted. Ok, so they all offer that bloody silly order form that allow us to input stops, but it seems there is not guarantee that the stop modifications will actually happen

So, the latest mod tells the bot to keep on trying to add stops etc even though the fucking bastard wanking shits have done their best to stop this happening.

I will defeat these bastards.

bool CheckTradingTimes(datetime Now)
{
   //Courtesy of George
   datetime MorningBeg, MorningEnd, EveningBeg, EveningEnd;

   //to switch to using real time, remove the "datetime Now" parameter from the procedure definition above and uncomment whichever one you want below
   //alternately, you can just call the procedure with TimeLocal() or TimeCurrent() as the parameter depending on what you want
   //datetime Now = TimeLocal();    //use local time
   //datetime Now = TimeCurrent();  //user broker time

   //we need to cast our conversions into the current date
   MorningBeg = StrToTime(TimeToStr(Now,TIME_DATE)+" "+ Start_TimeM);
   MorningEnd = StrToTime(TimeToStr(Now,TIME_DATE)+" "+ End_TimeM);
   EveningBeg = StrToTime(TimeToStr(Now,TIME_DATE)+" "+ Start_TimeE);
   EveningEnd = StrToTime(TimeToStr(Now,TIME_DATE)+" "+ End_TimeE);

   bool Morning = false;

   //Check normal case for morning , 7:00-13:00
   if (MorningBeg < MorningEnd && (Now >= MorningBeg && Now < MorningEnd))
      Morning = true;

   //Check to see if MorningBeg to MorningEnd spans 00:00, e.g. 22:00 - 04:00
   if (MorningEnd < MorningBeg && (Now >= MorningBeg || Now < MorningEnd))
      Morning = true;

   bool Evening = false;
   
   //Alert(TimeToStr(EveningBeg,TIME_DATE|TIME_MINUTES)," ",TimeToStr(EveningEnd,TIME_DATE|TIME_MINUTES)," ",TimeToStr(Now,TIME_DATE|TIME_MINUTES));
   //Check normal case for evening , 17:00 - 22:00
   if (EveningBeg < EveningEnd && (Now >= EveningBeg && Now < EveningEnd))
      Evening = true;

   //Check to see if EveningBeg-EveningEnd spans 00:00, 22:00 - 04:00
   if (EveningEnd < EveningBeg && (Now >= EveningBeg || Now < EveningEnd))
      Evening = true;
   
   return(Morning || Evening);
   
}//bool CheckTradingTimes()

SteveHopwood wrote:So, these mindless, turd-brained (and I use the term 'brained' with reservation), manipulative fucking bastards are forcing those of us daft enough to play their game ...

SteveHopwood wrote:Latest update in post 1.

George suggested a more efficient way of working out when to call CalculateDailyResult(0 in start(). View the comments I have left for an explanation.

George, you will be proud of me. I have removed a 'money-costing' variable from CDR.

gaheitman wrote:

SteveHopwood wrote:Latest update in post 1.

George suggested a more efficient way of working out when to call CalculateDailyResult(0 in start(). View the comments I have left for an explanation.

George, you will be proud of me. I have removed a 'money-costing' variable from CDR.

Excellent, we can all apply the savings to our trading accounts!