OK, I added a text file to 17812 describing my experiences. I heartily endorse the idea of a ‘back’ button! My narrative had to end when LC 8.0.1 refused to open any more property inspectors - no idea why. I also had to use the ‘fast forward’ button once, just go get some progress. It really does need to be more robust. I am still a long way from understanding widgets, I fear.
Graham > On 7 Jun 2016, at 20:11, Mike Bonner <[email protected]> wrote: > > Yeah, I forgot that. You actually have to go into custom colors to set the > rgb values, but it would be clear as mud to someone who has never done it > before. > > Definitely add to it.. If the tutorial tools can be fleshed out and made > easier, and more complete (hopefully with full storyboarding?) it would > help encourage a multitude of creative uses. (It might even be useful in > detailing "bug recipe" walkthroughs, as well as hopefully a way to include > tutorials in standalones.. I'd LOVE to include tutorials in at least one of > my standalones. (Lots of turnover at the place that uses this particular > application, and whlie its simple, having a tutorial walk a person through > the steps would be really great) > > On Tue, Jun 7, 2016 at 11:32 AM, Graham Samuel <[email protected]> wrote: > >> Well done Mike for getting your report in so quickly. I intend to add to >> it with a narrative of what I saw (on an iMac with Yosemite 10.10.5 running >> LC 8.0.1). I hope that Peter is right and that it’s all one problem, >> although there are other niggles than the guidance system - for example, >> when one is told to set colours, it would not be clear to a newbie that >> these are RGB colours, since the colour palette offers several alternatives >> and RGB probably doesn’t come up first… hoping to get on to my narrative >> soon. >> >> Graham >> >> >>> On 7 Jun 2016, at 18:51, Mike Bonner <[email protected]> wrote: >>> >>> http://quality.livecode.com/show_bug.cgi?id=17812 >>> >>> On Tue, Jun 7, 2016 at 10:16 AM, Mike Bonner <[email protected]> wrote: >>> >>>> ok thanks. >>>> >>>> On Tue, Jun 7, 2016 at 10:12 AM, Peter TB Brett < >> [email protected]> >>>> wrote: >>>> >>>>> On 07/06/2016 17:10, Mike Bonner wrote: >>>>> >>>>>> Yep. Should I assume add a report for each type of problem rather >> than a >>>>>> list of issues in 1, correct? >>>>>> >>>>> >>>>> Hi Mike, >>>>> >>>>> Since, as far as we know, these are all directly related to the same >>>>> feature and can likely be fixed together, please just file a single bug >>>>> report (and someone will split it up if necessary). >>>>> >>>>> Peter >>>>> >>>>> -- >>>>> Dr Peter Brett <[email protected]> >>>>> LiveCode Technical Project Manager >>>>> >>>>> LiveCode 2016 Conference: https://livecode.com/edinburgh-2016/ >>>>> >>>>> >>>>> _______________________________________________ >>>>> use-livecode mailing list >>>>> [email protected] >>>>> Please visit this url to subscribe, unsubscribe and manage your >>>>> subscription preferences: >>>>> http://lists.runrev.com/mailman/listinfo/use-livecode >>>>> >>>> >>>> >>> _______________________________________________ >>> use-livecode mailing list >>> [email protected] >>> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >> >> >> _______________________________________________ >> use-livecode mailing list >> [email protected] >> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode >> > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
