Ken, I normally do #3. I have looked at the code for stepconf and it's just a bit above my skills to try and add to it as it uses some clever coding.
If I knew how to submit a patch I would but I can't find any info on how this is done. It's another of those things that if you know it's easy but if you don't know it's impossible to figure out. If your going to add something to wiki on the subject I will not. Thanks John On 19 Mar 2008 at 8:25, [EMAIL PROTECTED] wrote: > There are a few ways to get things like, "The message needs to be > changed..." done. > > 1 -- Become a developer and make the change yourself. > 2 -- Submit a patch for inclusion by a developer. > 3 -- Submit either a feature request or a bug report via sourceforge. > > Mentioning it on this list might cause it to be done, but there is > little guarantee. #1, above, just gets it done. #3, above, makes sure > it doesn't get lost, but doesn't guarantee a time. Submitting a patch > (#2), may or may not get action. > > So...., I would suggest you get on sourceforge and submit a report. > > [Normally, I'd just drop you a note, but this comment is intended for > all those who have suggestions, requests, bugs, etc. The general > philosophy is that if it isn't written down, it doesn't exist. The > signal to noise ratio on this list is such that this doesn't count as > being written down for the purpose of getting something fixed.] Now I > guess I ought to follow my own advice and make sure the Wiki says > something like this. :-) > > Ken ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
