CONTACTS 

SUBJECTS
Save, F2

0403 -    ..
0404 - Summary/Objective
0405 -
040501 - Follow up ref SDS 3 0000, ref SDS 2 0000.
040502 -
040503 - Fixed two problems today that take longer to explain than to fix,
040504 - arising from recent improvements.  This record underscores the
040505 - challenge of avoiding new problems when making improvements, i.e.,
040506 - bumbling.
040507 -
040508 -     [On 010722 submitted updated to Wayne Wetzel. ref SDS 6 0001
040509 -
040510 -
040511 -
040512 -
040513 -
040514 -
040515 -
0406 -
0407 -
0408 - Problem
0409 -
040901 -  ..
040902 - 0702051  Macro 142, Save Function Failed Requires SDS Code Revisions
040903 -
040904 - Follow up ref SDS 3 TS7L, ref SDS 2 TS7L.
040905 -
040906 - An SDS report today is not finding a particular subject which is known
040907 - to be in a record.  This could be caused by a failure of the F2 save
040908 - function not archiving 01 subject pointers, or possibly the pointer
040909 - file has been corrupted.
040910 -
040911 - The record on 010712 has a subject code.....
040912 -
040913 -
040914 -               03 00050 01 05 02 06C 010712a
040915 -
040916 -
040917 - ....which is not showing up in subject reports. ref SDS 5 TX5K
040918 -
040919 - Examination of pointer files shows.....
040920 -
040921 -           week 26 beginning 010626 is not created.
040922 -
040923 -           week 27 has only one entry.
040924 -
040925 -           week 28 has only one entry.
040926 -
040927 - This record shows the pointer files since 010625 are not being created
040928 - correctly, which indicates the problem is with F2 save, supported by
040929 - 0702051.  Corrected the problem, per below. ref SDS 0 0800
040930 -
040931 -
040932 -
040933 -
040934 -  ..
040935 - 004  Make New Task
040936 -
040937 - Making a new task is not creating links to all of the headings.  Some
040938 - are being created, but not all.
040939 -
040940 - The record on 010712 is not being converted correctly to a schedule
040941 - task by 004. ref SDS 5 0001
040942 -
040943 - On 010323 the code in 004 was changed to improve this feature.
040944 - ref SDS 1 7L5I  It appears today, that the change was not
040945 - sufficiently comprehensive.  Did the work in the record on 010323.
040946 -
040947 -     Turned out the problem was that we were using the aw command twice
040948 -     from column 1 to position the cursor on the left margin to test
040949 -     that a line draw char that is used for headings, is being applied
040950 -     for a heading and not a diagram or other line draw function.  This
040951 -     was a mistake because heading lines that have multiple
040952 -     descriptions, are identified with a highlight flag for processing
040953 -     by 070405 to display on a web browser via Internet. The highlight
040954 -     flag was causing the 1st aw command on a heading with a highlight
040955 -     flag jumps to the first column of the heading instead of the dash
040956 -     in the line number field, since the highlght flag fills the space
040957 -     between the line number and the dash.  As a result, the 2nd aw
040958 -     command was jumping the cursor to the 2nd word in the heading
040959 -     instead of landing on the 1st word.  This caused the code to
040960 -     interpret the condition as not being a heading, because the
040961 -     beginning column of the narrative above the line draw char was
040962 -     different from the column of the line draw char, per the algorithm
040963 -     in the macro file, 004, reported on 010323. ref SDS 1 G14H
040964 -
040965 -     Correction merely required starting on column 8, which is the
040966 -     dash after the line number, and using a single aw command to get
040967 -     to the left margin.
040968 -
040969 -
040970 -
040971 -
040972 -
0410 -
0411 -
0412 - Progress
0413 -
041301 -  ..
041302 - 0702051  Macro 142, Save Function Failed Requires SDS Code Revisions
041303 -
041304 - Follow up ref SDS 3 0800.
041305 -
041306 - Line 650, ref OF 2 3162, -label nvMdn2
041307 -
041308 -    This is where we set up params to begin extracting and updating
041309 -    pointer files.
041310 -
041311 - Line 900, ref OF 2 QR6J, -label dBResto
041312 -
041313 -    This is where the problem occurred. The code uses setlen to
041314 -    evaluate for an empty file.  If a pointer file does not exist, then
041315 -    no records are read into the list of control field pointers.  This
041316 -    command needs to be called on screen line 3, but it was being
041317 -    called at the default location, and since in the case of week 26,
041318 -    no records were read into the file, it set a flag that there are no
041319 -    pointers because setlen was being called with the cursor below the
041320 -    end of file mark.  This occurred, because the end of file mark is
041321 -    moved to screen line 3 so existing pointers can be added below the
041322 -    new ones.  This facilitates removing existing pointers, if any, for
041323 -    replacement by the pointers in the current record being processed.
041324 -    If there are no existing pointers, then the end of file mark is on
041325 -    screen line 4.  Normally, there are always pointers, except when
041326 -    archiving a new record for a new week.
041327 - ..
041328 - Line 1090, ref OF 2 KP4G, -label exP
041329 -
041330 -    Set a flag to establish when a pointer file is emptied, because in
041331 -    that case the line positions change slightly.   Every SDS record
041332 -    has 01 control field pointers and an 04 record description.  But
041333 -    some records do not have 03 references to other documents nor 05
041334 -    pointers for contacts.  In that case, we need to read in the weekly
041335 -    pointer file and delete any pointers that might have been in the
041336 -    record previously, as occurs when such pointers are in a record,
041337 -    but later removed.
041338 -
041339 -    An additional command was needed to move the cursor above screen
041340 -    line 4 so that setlen command does not register an error.  This was
041341 -    accomplished by adding a command to locate the cursor on screen
041342 -    line 3, unless the file is emptied, in which case it needs to be on
041343 -    screen line 4, because screen line 3 will be the top of file mark,
041344 -    which also crashes the setlen command.
041345 -
041346 -
041347 -
041348 -
041349 -
041350 -
041351 -
041352 -
041353 -
041354 -
041355 -
041356 -
041357 -
041358 -
041359 -
0414 -