In this meetup, we 1) reviewed Dave Rogers’ “captain’s log” file and triaged unexpected behaviour he was having with his file, 2) Becker’s method of creating tasks that he creates during his writing process (NOTE: we did not complete the demo file during the meeting, @satikusala added conditional code to address the naming issue we were experiencing at the end of the meetup—see the example file).
var:string vSrc=$Name+“xID”+$Created.format(“dMY”)+““+$ID+””+document[name]; => will not populate - HowTo debug?
Hi everyone,
I have gone to great length to reproduce this little gem of a lesson, and I run into a strange issue. I’d greatly appreciate some help in debunking this situation.
So I started out with literally copying @satikusala’s example file that he built during the video. Ran into some issues, then, the next two days, rebuilt this very example file from the ground.
Now what’s my issue?
A var: string is set, like this:
var:string vSrc=$Name+“xID”+$Created.format(“dMY”)+““+$ID+””+document[name];
Then, further on, an attribute $Source(vNote)=vSrc; is populated with the above vSrc
This part, I could not get working.
Started over from scratch and still not working.
downloaded @satikusala’s demo file from the forum and started doing some comparing
still could not get it to work
Then:
I had already used show(vSrc) to have Tinderbox display vSrc => that worked allright
Then I added a user attribute and named it $PanETest(vNote)=vSrc; and added that to the displayed attributes as well, so in fact I have two identical attributes that are “named” differently.
Here, once you’ve tried the $PanETest check there were really only two possibilities, neither very likely:
Something crazy is happening which makes $Source unable to hold the result
Something is interfering with parsing the statement.
My first guess was #1, which was incorrect. After that, I wondered whether there might be an invisible character or illegal character in that line. I stared at it for a while in BBEdit, and it hit me.
You’re note alone. I experience this often enough. I agree with @eastgate’s breakdown, either 1) the code is not working, or 2) the action code stops executing after a certain point, which is often due to the semicolon missing, misspelled variable, etc.
