Is there a suggested best-practice when you need to make changes and additions to source code that will have to migrate when the next release of source code comes out? I have some minor tweaks we needed to make these great components even better and so I need to update the newest source code now we are moving to XE3 and gto the ImageEn update.
I am fortunate that these are fairly small and I can dig them out using a text compare. Most of them I took the precaution of marking with a conditional too.
I was just wondering if anyone else has come up with a slick way that could also be automated?
Second point. A couple of these are thngs that might be useful to others. Is ther a standard way of submitting suggestions (and code additions) for consideration?
I think it is best to comment them with a unique string, then uses a compare app to locate each of your changes and migrate them to the new version (which sounds very much like what you are doing).
If you have tweaks that you think are valuable to others, please email them with full details to me.
Thanks. I may send some stuff in a few weeks (when back from a work trip). None of it is earth shattering, but it is stuff we need and if I did not have to keep migrating it, that would be great. Basically have
1. Added supprt for Angstroms to the measure units 2. Added an OnAngleMeasure event
Search
Changing source code
Posted - Oct 04 2012 : 07:31:44
