One other thing that may be worth trying is to remove any non-native plug-ins and try again. I and several others have had issues with plug-ins designed and built with previous versions of LC.
For my home rolled plug-ins I checked them carefully and updated the ones I needed in LC8 and they are working fine now. For any third-party plug-ins, check to see if the developer has released an updated version for LC8. Since doing this I’m finding LC8 to be much more stable and I’m mainly using the DP to take advantage of and learn new features. Paul > On Jul 4, 2016, at 9:24 AM, Richmond <richmondmathew...@gmail.com> wrote: > > R. Gaskin is right (as usual): > > Develop on the Stable release. > > Try things out on the Developer Previews, get frustrated, and then file Bug > reports; > this is very important. > > R. > > On 4.07.2016 19:15, Richard Gaskin wrote: >> On the contrary, while I recommend using the most recent "Stable" build for >> deploying, for development I strongly recommend using the most recent build >> with any designation specifically so we can identify and resolve these >> issues ASAP. >> >> Waiting until after final release only guarantees a previously-unknown issue >> will remain in the final release. >> >> @Lagi: Please submit two bug reports, one for the crasher since of course >> crashers need to be resolved ASAP, and another for the text baseline since >> no one wants newcomers getting turned off from LiveCode the moment they drop >> a control onto a card because it looks wonky. >> > > > _______________________________________________ > 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 _______________________________________________ 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
