Disliked
Hi Pip2,
From the confirmation point, it looks like we will need the OT3MA separately and so there is no need to combine it into TSS, I think. Since I started that, I would like to record that now I have changed my mind! They can be (have to be) separate to work best.
chandraIgnored
As far as TSS and OT3MA being separate indicators, if the two are saved as one template, it will be easy (simple) to attach them to a file when needed. So there's not much to be saved in time by combining them. All I can foresee is more problems de-bugging something that does not really have to be!
Aubrey, good point, I can (and will) write an update in the zip folder in the readme file therein. So everything will be in one place. Why didn't I think of that?
As far as your 376 query, I can't help directly, my broker's time is offset to my local time too. I made up a table with 2 columns, the left column is for Broker time (24 hr clock) and the right column is my time (am/pm).
I never get confused because my time table is at my elbow at all times. Its a bit of a pain but it works.
I decided to edit this post rather than post a new one. Something just came to mind. How about "CandleTime" program? If someone could make it display EST instead of countdown time to close of bar 0, that will solve your problem. The display of the time can be shifted so that it is in a convenient spot. The actual source for the CandleTime is very short, barely 20 lines of active code. Food for thought.
Cheers,
Pip2