On Oct 27, 2014, at 10:24 PM, Kay C Lan <lan.kc.macm...@gmail.com> wrote:
> http://quality.runrev.com/ > > and report your findings and the simple steps required to see the > 'failure'. Attach (upload) both stacks so they can see exactly what you are > seeing. > > If your stack contains confidential information that you'd rather not share > with the Runrev team, then you'll have to build a new stack with a couple > of cards that reproduces the problem. This of course is a good thing > because if you can, the problem is what you suspect, but if your new stack > doesn't exhibit the same fault, then it isn't what you suspect and there > must be other factors that are causing the problem. You’re right of course. It’s kind of a chore. Sigh… I guess I’ll get started. I was hoping someone else would confirm the same bug in a less cumbersome, non-confidential stack, but that hasn’t happened yet. It will happen eventually. By then, it might be a known bug or a fixed bug. Paying it forward…. Tim Miller _______________________________________________ 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
