here we go again :) On Thu, Aug 19, 2010 at 11:29 AM, Thomas D. <madsc...@gmail.com> wrote:
> > For me this is an issue I have to deal with quite often, - so I'm very > humbly going to put my 2 cents in. > I will contribute 2 cents also > > I realize that probably everyone has their own idea of what the ideal > solution is, and wholeheartedly respect that what may seem to be a > "minor" change from a user perspective can often be massive work from a > developer perspective but ideas never hurt so here are mine. > cannot disagree with this statement It seems to me that just having a configuration option somewhere, or a > register, or a parameter, or a menu choice somewhere - such as whether > to treat the condition as an error, warning, or silent, and knowing the > result - would help to solve the "desired" unknown. For myself, in most > situations it would be very convenient to just follow the path and leave > what it cannot reach, - for other machinery or users or applications it > might be unacceptable and an error condition could be a life-saver. I > believe flexibility, where possible is always desirable. > wholeheartedly agree here!!!!!!! thanks Stuart -- dos centavos ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
