Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Fat Tails - Tried doing what you and Big Mike suggested - Attached are the initial Error logs for the export compile 'OpenRangeFH - Error msgs.xls' and the files 'anaOpeningRangeV23FH.cs' and 'anaOpeningRangeV23FHb.cs'. The Error logs 'OpenRangeFH - Error msgs.xls' pertain to 'anaOpeningRangeV23FH.cs' which did compile and plot but won't export. I then tried changing all instances of OR23 to FH23 and saved that as 'anaOpeningRangeV23FHb.cs". This version 'FHb' will not compile at all and the error msg log 'OpenRangeFHb compile - Error msgs.xls' is attached.
I can't figure out what needs to be changed to export for others. If this is to much work i can just leave well enough alone, as the indicators work just fine for me.
The error message clearly shows that the problem is related to the use of enums. If you have an indicator which uses an enum from another indicator, you cannot export it. As you created copies of the original indicator, you need to replace the enums - not only the definition in the region Global Enums, but also all the lines where it is used.
As you have put it now, the indicators you want to export use the enum of the original indicator, so they cannot be exported without the original indicator.
Just scan your .cs files for "anaPlotAlignOR23" and replace this with "anaPlotAlignFH23", wherever you find it!
When you use ET as time zone abbreviation do you mean Eastern European Time (Europe) but should be EET or Eastern time zone (North America) should be EST ?
If ET = Europe Time independent of summer or winter time then why is the RUSSELL defined using the Europe Time ? If i look at the values you seem to refer to the Eastern time zone.
There is a difference between Eastern Time (ET) and Eastern Standard Time (EST). EST does not undergo the daylight savings schedule, ET does. So I am correctly referring to ET, not to EST. Please read link below.
Wiill put the indicators in the download section, but now just testing and awaiting feedback. There may be some bugs, and I also plan another version during the next few days.
I am still working on a way to display the different ranges and have been busily coding.
I want to have a look at the following ranges and integrate them in my trading.
(a) night session range (gray)
(b) European session (not yet coded)
(c) opening range (duration and beginning selectable, red )
(d) pivot range (range between PriorMidLine and 2*PP-PriorMidline, blue)
Example below:
Any suggestions, how to improve the concept?
Currently reading the book "The Logical Trader" by Mark Fisher and applying some - not all - of his concepts.
Fat Tails - looks really good. Would like to see the times for sessions user selectable, eg., European Session time frame I really only want to look at the 2AM - 5AM CST range.