On Friday, August 23, 2002, at 11:54 AM, Rich Mooney wrote:
> I want to thank everyone, especially Dar, for their suggestions on this > problem. I've finally solved it but, I don't really understand why. > In my > core serial communication handler I have some code which records > everything > sent to or read from the serial port to a field. This was actually the > first thing I looked at when I found out about this problem because I > hadn't > set any limit on how much info could be written to this field except > that I > made sure it was emptied on startup. This was obviously a problem for > software that had to run 24/7. I addressed this issue by having my > code > delete the oldest entries if the field grew to more than 200 lines. > If I > turn off this feature so that nothing is written to this field, my > software > no longer slows down. As I mentioned earlier, if I run the software > without > being connected to the system the software doesn't slow down even if I > am > writing to that field. Here's a sample of what gets written to the > field if > I'm not communicating with the system: > > > > Local refers to stuff I'm writing to the port while remote refers to > stuff > I'm reading from the port. It makes no earthly sense to me at all > that this > should make a difference. Anybody have any ideas? Have you tried writing your log file to a custom property instead of a field? I believe that writing this to a field has more of a penalty on the cpu. You could then pull the data from the custom property and put it into a field to be printed over viewed when needed. Just a thought... Best regards, Mark Talluto http://www.canelasoftware.com _______________________________________________ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard
