Stormin_Norman
Currency Trader
- Joined
- 12 January 2008
- Posts
- 1,256
- Reactions
- 0
yeah in the indicator properties (right click chart, indicators, select, properties).
also turn off all the prices and writing on the chart to get rid of the writing at the top left and the currency prices.
u can then pull the graph up using a resizing cursor to just below the indicator's green writing.
also u can adjust the time on the chart, which will show u different time periods on the EA.
you should start a seperate thread to discuss your EA.
do we get a summary of what they are and why theyre good?
Well, I've taken a few steps forward. I'm finding it a bit overwhelming to learn MQL4, but in the meantime I've been learning VBA and have setup a spreadsheet to autotrade FX through IB. Have to wait till Monday now though before I can start testing it and debugging. It's not as simple as it seems to me as a programming beginner to encode human logic and have the PC check for all the possible conditional decisions needed to cover all bases. I'll get there though and am looking forward to this next stage in my trading journey.
I can now better appreciate those of you who have written EAs or other programs from scratch. Kudos to you.
Ps. Question for VBA programmers. In terms of processing usage and efficiency is it better to use more or less modules? As a complete noob, I'm finding it simple to write lots of little modules that do specific tasks and then write an overlay kind of module that calls the little ones as needed - but I'm not sure if that taxes the PC's processing too much?!
One tool that can greatly assist a programmer dealing with logic issues is the Karnaugh Map. You can use these to simplify expressions of multiple conditions into just a few lines of code. Learning to use these makes life sooo much easier when dealing with, say, long entry, long exit, short entry and short exit signal combinations.
As for VBA modules. IMHO if you are only ever going to use the functionality of that piece of code one just write the code inline. If you're going to use the functionality in a few different applications then write a module and save it so it can be reused.
If you write a module, you can write a small application that extensively tests the module so you know it works.
The short time taken to write a proper test-rig for the function will save many hundreds or thousands of hours bug-hunting later!)
Can you expand on this a bit more please? What I've been doing is have a module do something arbitrary as a test, which I can then replace with the real decision once I know it's working.
For example: I might want to place a buy given X being true. So to test that module, if X then print the current time in a certain cell or write "Hello" somewhere. So I know that part of the overall tree is working. Then when I live test, I just replace that outcome with order placing code instead.
But I get the feeling you might mean something else.
Thanks wabbit. No doubt that was simple to you, but I'll need to read it a few times and try it out to make sense of it.But thanks!
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?