pete at lcsql.com
Tue Sep 1 19:20:00 EDT 2015
Hah, thanks for that Mark. You are correct, now I see the errors. Did I
miss that somewhere in the thread?
Going back to the original issue, I guess I should track down the code in
the stsMXLEditor plugin that sets the script and set explicitvars before
and after it. That will work for me because I use strict compile mode and
want these errors to show up but would cause a mess for folks who don't use
strict compile mode.
Perhaps the right way to do it would be to set explicitvars to the value of
the strict compile mode option or provide an option within stsMXL itself.
Unfortunately, don't have time to do that right now.
On Tue, Sep 1, 2015 at 3:53 PM Mark Wieder <mwieder at ahsoftware.net> wrote:
> Peter Haworth <pete at ...> writes:
> > Entered bug report 15849 for this.
> Thanks for filing that.
> What's going on is that the editor preference for 'Strict Compilation"
> doesn't do what you think it does. It only allows checking for errors
> in the IDE's script editor (which is why it's in the script editor prefs).
> What you really want to do is
> set explicitVars true
> before setting the script. Then you'll see the proper error result.
> Add this to the top of your mouseUp handler and see the difference.
> Why are there two settings?
> The IDE's system scripts are riddled with bugs. If explicitVars were
> enabled then errors would be seen and the team would have to fix them.
> This would take time away from adding bloat^H^Hnew features.
> Mark Wieder
> ahsoftware at gmail.com
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode