RHKluckhohn
Active member
Wondering if somehow they've tweaked the error checking in build 105766 while we weren't looking --
Twice in the last couple of days the Set Junctions rule has thrown me a red bug for a "junction not found" error. One was in a session I put on the DLS back in September, which had tested OK then but had an entry for a non-existent junction. Today I ran the Kickstarter County "Morning Run" session and the same thing happened -- a Set Junctions rule showed an entry for "ECHO_junction," which is nowhere to be found by search either with FIND or by looking at the most likely suspects.
I've fixed the issue in my own session and uploaded it but there's nothing to be done for the KC session, of course. In my own case it could have been a hold-over from the original 12 version though I don't remember renaming any junctions.
:B~)
Twice in the last couple of days the Set Junctions rule has thrown me a red bug for a "junction not found" error. One was in a session I put on the DLS back in September, which had tested OK then but had an entry for a non-existent junction. Today I ran the Kickstarter County "Morning Run" session and the same thing happened -- a Set Junctions rule showed an entry for "ECHO_junction," which is nowhere to be found by search either with FIND or by looking at the most likely suspects.
I've fixed the issue in my own session and uploaded it but there's nothing to be done for the KC session, of course. In my own case it could have been a hold-over from the original 12 version though I don't remember renaming any junctions.
:B~)