Errors when Compiling a Nettalk app

[Richard I]

Errors when Compiling a Nettalk app
I have the same reoccuring error on compile
when I select the error from the error pad the CLW opens showing the error which, in this case  is  one too many open brackets.
The error window displays the location as  "Global Declaraions"  the second heading field is  "Page Header Tag "
I dont seem to be able to get to the code embed to correct and save

I can fix in the  Clw and compile and save but its only good for one time
The error returns on the next compile

In Tools
Application Options
in the IDE tab-
I have unticked "edit embedded source errors in generated code"
and in Embed Editor tab -
I have both editing options ticked ON
ie" Edit errors in context"
and "Edit source embeds in context by default"

I have tried various combinations but the  CLW always opens for the edit

What do I do to correct the settings please ? so that
a. that the clw saves and survives recompile
b. the error pad opens the embedded code directly
Thanks
Richard
NT 12.41

[Richard I]

Appear to have fixed the compile issue by OMITTING in source of the PageHeaderTag and dropping, without the offending ( , into the blank embed point below it.
Cheers
Richard

[Bruce]

Hi Richard,
it's helpful if you post the offending CLW as a zipped attachment please.

Cheers
Bruce

[Richard I]

Thanks Bruce
The line is in  Task Panel header - 'Logout' and is identified by a run of **************************

I suppose the abbreviated question could be "Why can the embedded code not apen automatically on edit?"
or
"Why does the CLW always open?"

regards
Richard

[Jane]

I suppose the abbreviated question could be "Why can the embedded code not apen automatically on edit?"
or
"Why does the CLW always open?"

regards
Richard

Hi, Richard,

The magic "I want to open the app on errors" settings do work.  Usually.  Mostly.  Except...

Try the attached example.
As it is, it will throw an error and open in generated source, not in the app.

Now fix that error and create a different one:

1. In the embed code, add the missing END for the CASE statement (to fix the existing error)
2. change one of the variables to LOC:A (which is not defined).

Now attempt to compile, and the error will open in the app, not in the source.

Apparently trying to open in the app just can't figure out where to go when there's a bolloxed END....

Cheers,

Jane

[Richard I]

Thank you Jane, for your reply and example, which I will look at.
Meanwhile, Im hoping you can comment on:
1. the CLW attached earlier appears to have been created in the template as I cannot get to it although I dont recall how I got the commented area in in the first place...
2. you say "the magic "I want to open the app on errors" settings do work.  Usually.  Mostly.  Except..."
OK but which setting is that because thats what I want.
OR have the CLW changes actually save..and stay saved

In anticipation,
best regards,
Richard

[Jane]

I think this is what you're asking about, Richard.  (Remember that you can only edit application preferences when you do not have an APP open.)

[Richard I]

Thanks Jane, that clarifies the settings
Ill check the example under those settings
Cheers
Richard