I was thinking of having a debug level of messages interspersed in the config files that when read would build a display of the program flow with a 'token' showing where the control flow is currently. This would allow a debug to pinpoint the stopping point and also watch the flow during the development phase.
this is just my idea of a possible solution to 'shop owner resistance' On Mon, Jul 23, 2012 at 10:18 AM, cogoman <cogo...@optimum.net> wrote: > On 07/23/2012 10:45 AM, Stuart Stevenson wrote: > > Maybe a debug gui with message tags at various places in the software to > > display the control flow and where the current tag is stopped. > Are you thinking of a program to comb through the log files looking > for error messages that we know how to fix? > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > -- dos centavos ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
