wait with messages

[Scott Rossi]

I feel your pain.  We're all in (or have been in) that boat.

But I would ask, in what environment is this NOT the case?

In addition to LiveCode, I go through this almost every day with HTML, CSS, Javascript, Flash, ecommerce admin tools, and many applications.  In years of creative work, I have almost NEVER been able to finish a project without having to research or in many cases ask for help, because the detail/feature I wanted to implement was too specialized for the documentation (if there even was any).  Just the other day I spent an entire day trying to work out a file download issue with LiveCode server and HTML.

Fighting with the tool/environment is not unique to LiveCode.  At least with LC we have helpful folks on this list, in the forums, and those writing books.  Not sure how I would get stuff done without those people.

Regards,

Scott Rossi
Creative Director
Tactile Media, UX Design

> On May 1, 2014, at 10:30 AM, <larry at significantplanet.org> wrote:
> 
> What really BUGS me about LiveCode is that the documentation (example, wait with messages) is SO sketchy, that you cannot figure out how to use it.  I'm constantly wasting my time fighting something that doesn't work and then ending up having to do a workaround as shown above.