John Zeman wrote:
> In addition to what the others have said, here is another way you can
> think about NoteTab ini files.
> In a clip at the point where you are ready to do something with the
> ini file, the first step is to save the actual dynamic settings of
> the ini file (which is contained in Windows memory) to disk by file
> Then write whatever changes you want to the ini file immediately
> after that. Finally, you'll want to reload the ini file back into
> Windows memory again by using
> For example the following simple clip adjusts the NoteTab ini file
> (regardless of what it is at the moment in Windows memory) to set the
> widths of the Clipbook, Quicklist, and outline columns to 150 pixels.
> ^!SaveValue Clipbook:PanelWidth=150
> ^!SaveValue Quicklist:PanelWidth=150
> ^!SaveValue OutlineList:PanelWidth=150
You may be correct but I would like Eric or Jody to verify the above.
It seems the sequence is a little off.
Shouldn't the ^!ProgIniSave command be immediately after the ^!SaveValue
commands to allow all the most current information entered or saved to
be written to disk then followed by ^!ProgIniLoad to load the newly
saved disk file back into memory with all its up to date changes intact?
This is the command order I would use but I could be wrong, thus the
call for clarification from 'above'.
One, also, may have some success using the ^!Setinifile command to close
an ini file in use then re-use it to re-access the same ini file.
hrs > hsavage@...