Upgrade, Stack Toolbar, New VOL and AVG VOL and LBL Markers, IB TWS Window

January 19 , 2006

Stack Toolbar

17:06 @Ensign-Howard: let me give a little training update about the stack toolbar

17:06 @Ensign-Howard: as per suggestions from class yesterday, the alignment button will only operate on this chart who currently are physically covered by the stack top chart. Thus the charts withs same symbol and time frame elsewhere will not be pulled into the alignment.

17:06 @Ensign-Howard: Also, every use of the toolbar will update its tabs, which can have a nice benefit in this manner:

17:06 @Ensign-Howard: Say there are 5 charts the stack, by clicking on the 5th tab, that chart goes to the top and a new chart is now on the 5th tab without moving the mouse I can continue to click and click and click and rotate through the stack of charts.

17:07 @Ensign-Howard: I like this reordering of the tabs automatically as a new chart goes to the top.

17:07 @Ensign-Howard: If you want to just rotate between 2 of the 5 charts, put mouse on 2nd tab and click multiple times and you rotate between 1st and 2nd chart on the stack, and the bottom 3 are not in the rotation.

17:07 @Ensign-Howard: kind of cool

17:08 @Buffy2: yes I like that Howard

17:08 @Ensign-Howard: Enjoy the new VOL, VOL with bar is average volume, and LBL for labels from DYO line

How to have the line tool draw both vol and avg vol:

LBL Marker

7:26 @Ensign-Howard: ok, I can answer questions

17:26 @Ensign-Howard: first ? please

17:26 @Buffy2: how?

17:26 @Ensign-Howard: use LBL marker on a DYO and the text for the marker is <-+-+- -+-+-> : the < and > decode to arrow shapes and the alternating - and + give the crossed line effect and had a couple spaces in the middle for the gap

17:27 Shar: Can you show the dyo please Howard.

17:27 @Ensign-Howard: I have erased it but will recreate it, 1 moment

7:32 TOC: you were able to make the GV idea with label work...i saw that you were finding issues earlier

17:32 @Ensign-Howard: oh it will post value, but it is the GV value at the end of the calculation. What you will not get is the GV value at any particular bar in the chart. The calculate is across all bars, and thus GV is a last bar value.

17:33 @Ensign-Howard: Then the draw phase happens and the marker finds a static last GV value to use. There is a work around however, and that I will demonstrate because it is not obvious to you. Let me post example

17:34 TOC: great

17:35 @Ensign-Howard: in this example I have 2 DYO lines, and Line A value is written to [2] and then Line B is trying to show the label which is the contents of [2]

17:36 @Ensign-Howard: Notice that for every label on the chart they are a constant value of 1290.46. That is the last value written to [2] in the calculate phase.

17:36 @Ensign-Howard: Now let me show you the workaround

17:38 TOC: clever

17:38 @Ensign-Howard: The difference in this example is the label is the [B] value and there is a unique value of line B for every bar. So as we draw at a given bar position, we can read the [B] value that was stored which was the value of [2] at that time during the calculation phase. So though we are now in the draw phase, we have a history of the [2] values at each bar position. So I am using Line B reference of [B] instead of the GV reference of [2] in the label

17:39 dblue2: cool

17:39 TOC: will LBL read the next variable it finds in the DYOS?

17:39 @Ensign-Howard: now I have the various values during the calculate phase that are the history of Line B

17:40 TOC: so the value that is being posted is actually the value of the MA from the prior bar?...or the current bar?

17:40 @Ensign-Howard: LBL can be anything you want, text plus GVs (though GVs not recommended), and DYO Line values, and Bar look up values such as [$H] etc. [2] is the current bar average value. If you want prior value then use offset -1

17:41 TOC: ok...was just making sure I understood...TY so very much Howard

17:41 @Ensign-Howard: welcome.

17:41 @Ensign-Howard: Anyway, since we have GVs that can be in labels, I am not going to implement separate markers for GVs. I do not suggest that GVs be in labels or markers anyway because of this ending value issue. GVs are a final value, and not a per bar value when we get to the draw phase and I do not want to do a draw bar by bar during the calculate phase because then repaints would require recalculation and that would greatly slow down the program when windows are uncovered and need to be repainted.

17:42 TOC: makes sense...i believe this will enable the study that we were working on. Would checking "close only" resolve that issue?

17:43 @Ensign-Howard: Not a close only issue

17:43 TOC: ok

17:43 @Ensign-Howard: The root of the issue is we calculate across all bars, and then we draw across all bars

17:44 @Ensign-Howard: We keep the phase of calculate separate from the draw. Draw is called by such actions and changing your chart scale, or bar spacing, or moving a window across another and the space needs to be redrawn, but not recalculated. Calculation can be time consuming.

17:45 @Ensign-Howard: You also have VOL marker which is the sum of the volumes across the span, as in the pesavento patterns tool and the VOL with the solid line on top is the average volume. That is VOL divided by the number of bars in the sum. Looks cool, and like your example yesterday

17:47 TOC: The purple line is a Drawn Line?

17:47 @Ensign-Howard: The Pesavento Patterns tool also has a new Left Location check box so the text can be posted on left side of the point instead of the right side.

7:47 @Ensign-Howard: The purple line was a draw line with the AVE VOL marker at its right side. So 10200 is average volume for the span of the purple line

17:48 TOC: oh nice...so we now have a third location on the pesavento tool

17:48 @Ensign-Howard: toc, you really have 4 locations

17:48 @Ensign-Howard: 2nd and left can be checked or unchecked as a mix - so you have right / left, and high / low giving you 4 locations

IB TWS Window