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 ----- Original Message ----- From: "John Thornton" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, March 19, 2008 8:12 AM Subject: Re: [Emc-users] Emc-users Digest, Vol 23, Issue 44 > John, > > No one could possibly guess or assume that the message only prints once. > The message needs to be changed to state that it will only appear once. > > John > > > On 18 Mar 2008 at 19:27, [EMAIL PROTECTED] wrote: > >> Gene Heskett wrote: >> >> > In re the rtapi and unexpected realtime delay issues, I experimented >> > some this afternoon with my base thread which was set at 78000ns >> > when I started, reducing it to 38000ns for the last test, running >> > most of the stuff in the nc_files dir to test, and never did see >> > another error AFTER the startup, even when running at 200% speeds >> > here. >> >> You never will. >> >> The realtime delay error message is printed only once, the first time >> EMC notices a delay. We don't print it every time because if you have >> your period set too low, or you have a computer with bad realtime >> issues, you could get hundreds or thousands of those messages every >> second. >> >> Only printing the message once solves that problem, but it means that >> you really don't know how often you are getting a delay. But DON'T >> think just because you get it only once that it is happening only >> once. >> >> Regards, >> >> John Kasunich > > > > ------------------------------------------------------------------------- > 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 > ------------------------------------------------------------------------- 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
