<?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:office:smarttags" /><st1:City w:st="on"><st1
lace w:st="on">Phoenix</st1lace></st1:City> is based on a former EA: Firebird (made by traderSeven). See the manual for further information. Of all the EA’s I tried, Firebird was the first EA that had the potential to make some money. On the other hand it had some bad habits that could result in a seriously drawdown of your account. <st1lace w:st="on"><st1:City w:st="on">Phoenix</st1:City></st1lace> is an attempt to preserve the best of Firebird and to prevent the drawdowns of your account. <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o></o>
<o></o>
Maybe it’s too soon to launch <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City>. I didn’t get the time to make all the necessary tests or implement proper error-controlling mechanism. Furthermore some parts need a little tweaking But Wednesday next week I will have my vacation but before that I want to deliver a bug-free <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City>. So my request to you is to test this version and give me as much feedback as can before next Wednesday!<o></o>
<o></o>
As starter of this thread and maker of <st1lace w:st="on"><st1:City w:st="on">Phoenix</st1:City></st1lace> I think it’s just to make some rules. Well in fact only one: of course you are free to adapt <st1lace w:st="on"><st1:City w:st="on">Phoenix</st1:City></st1lace> in any way you want, but please don’t post it in this thread! I want to keep the code of <st1:City w:st="on">Phoenix</st1:City> as clean as possible and want to prevent that in the end too many versions of <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City> are circulating in the same thread and nobody knows what version is doing what. <o></o>
<o></o>
If you think that you have a useful addition or modification for <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City>, you can post it in this thread. We can discuss about it and when we all agree I can implement it in <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City>.<o></o>
<o></o>
I will use this first post for the updated versions of the EA, the indicator and the manual.<o></o>
<o></o>
That’s all. Let’s give it a try!<o></o>
<o></o>
In the ZIP-file you will find the following files:<o></o>
<o></o>
Phoenix_EA_v1_0.mq4– the “Expert Advisor”<o></o>
Phoenix_IND_v1_0.mq4– the indicator to make the SafeArea visible (seen manual) you don’t need it for the EA to work!<o></o>
Phoenix Manual v1.0.p
Update 07/14/06:
Version 1.1
- Use the setting RoundupLots=true if your broker don't accept Lots like 0.24.
- Is now working for MicroAccounts
- Corrected a problem with GambleNow and MM
- SafeArea was not working for EURJPY. Now it does.
<!-- / message --><!-- attachments -->
lace w:st="on">Phoenix</st1lace></st1:City> is based on a former EA: Firebird (made by traderSeven). See the manual for further information. Of all the EA’s I tried, Firebird was the first EA that had the potential to make some money. On the other hand it had some bad habits that could result in a seriously drawdown of your account. <st1lace w:st="on"><st1:City w:st="on">Phoenix</st1:City></st1lace> is an attempt to preserve the best of Firebird and to prevent the drawdowns of your account. <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o></o><o
></o>Maybe it’s too soon to launch <st1:City w:st="on"><st1
lace w:st="on">Phoenix</st1lace></st1:City>. I didn’t get the time to make all the necessary tests or implement proper error-controlling mechanism. Furthermore some parts need a little tweaking But Wednesday next week I will have my vacation but before that I want to deliver a bug-free <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City>. So my request to you is to test this version and give me as much feedback as can before next Wednesday!<o></o><o
></o>As starter of this thread and maker of <st1
lace w:st="on"><st1:City w:st="on">Phoenix</st1:City></st1lace> I think it’s just to make some rules. Well in fact only one: of course you are free to adapt <st1lace w:st="on"><st1:City w:st="on">Phoenix</st1:City></st1lace> in any way you want, but please don’t post it in this thread! I want to keep the code of <st1:City w:st="on">Phoenix</st1:City> as clean as possible and want to prevent that in the end too many versions of <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City> are circulating in the same thread and nobody knows what version is doing what. <o></o><o
></o>If you think that you have a useful addition or modification for <st1:City w:st="on"><st1
lace w:st="on">Phoenix</st1lace></st1:City>, you can post it in this thread. We can discuss about it and when we all agree I can implement it in <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City>.<o></o><o
></o>I will use this first post for the updated versions of the EA, the indicator and the manual.<o
></o><o
></o>That’s all. Let’s give it a try!<o
></o><o
></o>In the ZIP-file you will find the following files:<o
></o><o
></o>Phoenix_EA_v1_0.mq4– the “Expert Advisor”<o
></o>Phoenix_IND_v1_0.mq4– the indicator to make the SafeArea visible (seen manual) you don’t need it for the EA to work!<o
></o>Phoenix Manual v1.0.p
Update 07/14/06:
Version 1.1
- Use the setting RoundupLots=true if your broker don't accept Lots like 0.24.
- Is now working for MicroAccounts
- Corrected a problem with GambleNow and MM
- SafeArea was not working for EURJPY. Now it does.
<!-- / message --><!-- attachments -->
