J. Landman Gay wrote:
What usually stops me is the need to create a separate, stripped-down
stack to demonstrate a more complicated bug. I completely understand
the need for this, especially in my case where the original stack is
huge and complex, and I wouldn't expect RR to plow through all that.
But extracting the exact set of circumstances that reproduce the
problem
without including all the surrounding code can sometimes be a whole
afternoon's work or more, so I don't do it. I just hope someone else
has a simpler example and will report it for me instead.
I know when I do this that I'm not helping myself very much, but
there's too much going on to do otherwise.
No shame in that, or if there is I'm just shameless 'cause I do that all
the time.
Like you, I recognize that not pinning down a recipe won't help me get
it fixed, but like RunRev themselves we all have to balance the desire
for completely air-tight work with the realities of keeping the doors
open.
--
Richard Gaskin
LiveCode Community Manager
rich...@livecode.org
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
