Message Path Question

[marksmithhfx]

Hi Mark,

What's happen if you replace "last cd" with cd &&the num of cds like this :

Best

Jean-Marc

Hi Jean-Marc, looks good to me

[jacque]

To compile a script means to click the Apply button. Every time you change/edit a script, you need to Apply (compile) it before you do anything else. You can't debug a script that has not been applied. Saving the script is not the same as compiling it; you need to specifically click Apply. Closing the script window without compiling, even if you save it, will lead to the issues you are having.

An uncompiled script in the card means that card no longer has any script at all. That's why the button can't find it. The button script will open because that's where the error first occurs. Because the engine thinks the card has no script, it can't open that one.

To fix things, open the card script. Make an insignificant change so the Apply button will enable. Then click Apply again. You should see some errors. Fix them, Apply again. If there are still errors, fix those. Apply again. Continue until you no longer get any errors. A successfuly compiled script will have a green dot in its script tab at the top of the window. Until it compiles, the engine will not think the card has a script.

There are two kinds of errors: syntax and execution errors. You must have the syntax correct before you can begin to debug the execution.

[FireWorx]

To All of you and especially to Jaque,
Thank you for sticking with me until I figured this out. The problem being I had the "Toggle the script editor tool bars" button selected in the far right upper corner of the script editor window. Thus the "Apply" button was hidden. Everything is working great now and I have a much better understanding of the entire process. After 15 years of working with HyperCard, MetaCard, Revolution, and now LiveCode this little SNAFU really had me tearing my hair out!
Best to you all! Thanks Again!
Dave

[mwieder]

Wow! I've never noticed that button before. Why is that there? And it has some screen refresh problems, at least on linux.

[mwieder]

...but anyway, congrats on figuring it out - it had the rest of us stumped as to why you were getting weird results and nobody else could reproduce them.

Now get back to work. <g>

[jacque]

Ohhhhh.....I NEVER would have thought of that! I knew the button was there but I never change it. Good sleuthing, Dave.

Must scribble this into my mental notes of things to check on when someone has issues. We get so locked into our own habits that we miss the obvious.

[SusanB]

I, too, was having the same issues. So glad I checked here!

[marksmithhfx]

I, too, was having the same issues. So glad I checked here!

Sounds like a user interface issue that could cause a lot of frustration. Glad you found the solution!

-- Mark

[spencer]

Try deleting your preferences file. I had that in the Dec. Game Academy with class stacks. It went away, don't know why;
might have been that "strict compilation" mode was checked, so it was not able to execute due to local variables that were undeclared. My "apply" button was visible. Might have happened that I closed the script editor window without clicking the "apply" button. Now when I edit the script, say, add a line, "put foo into tTest", do not click "apply", and close the script editor window, and save the edited script, run it, the new variable tTest has foo in it. But I'm in LiveCode 5.02, and started in 5.00, so maybe it was fixed. Like you, I went through way too much work testing what was wrong. Those preferences files should be our first place to to look for a solution.