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)
I did think about that and my rational is most users just want the new indicator to overwrite the old one since they are not programmer. A select few( say a hardcore programmer) will want to preserve the old version for the safekeeping purpose. Balancing between the two I will rename the indicator if there is a significant change otherwise it stays the same.
if you update an indicator you should give it a diff. name (means to give the version number not only in the .zip but also as real indie-name via "save as .... VolStop_V3_3 iE) - i think its really important!
We had this game with our DMAs + also sharky knows storys about this.
if i integrate indies in charts +/or strategys and mess that up with importing + overwriting - that brings really trouble.
if you have diff. versions everyone can decide if he deletes the old ones. that hurts no one.
if the stuff gets overwritten this can cause a pretty chaos.
cory, it is still a good idea to include the version numers so that anyone using it knows which they currently are using... of course if it is just for yourself... no one else cares... but if you are sharing it, and you post a chart... and someone else has the same chart, same TF but it doesn't look like yours, it is easy and quick to resolve by checking the version number... v1_3 where 3 is changed from 2 on minor changes, etc.
I posted suggested coding standards in the Programmers Paradise forum. I wrote these after the nightmare of the flurry of coding activity in June... a sharky indicator... no one knew what they had and it was very confusing and very frustrating for everyone involved.
Here is my first cut at suggested coding standards for futures.io (formerly BMT). I welcome comments and suggestions... following these simple guidelines will save us all a frustrating experience such as RJay posted today.
