Hi Bryon--
Yes, because the change tracking metadata is stored in the document, including whether CT is turned on for that document or not. (This is done via namespaced markup, which you can see if you open the file in a text editor after saving this way.)
If you want it to behave more naturally, so that the CT metadata doesn't trigger the "dirty" bit on the document that causes it to prompt for save when you close it, you could add a line to your editinit to clear the modified flag immediately after enabling CT. So your ACL file would look something like this:
set changetracking=on;
modified(0,0); # first zero means "current doc", second zero means "mark as not modified"
Now, if no further changes are made, you shouldn't get prompted to save. But if other changes are made, they will flip the modified flag back on, and you'll get prompted as usual.
I'm not sure what you mean by "the track changes bar". If you mean you want to dock the Accept/Reject changes dialog to the top of the edit window, you can probably do that with some ACL code. Try something like this in your editinit:
require _chgtrk;
$ct_win = _chgtrk::OpenDialog();
$ct_doc = _xmldlg::getWindowDoc($_chgtrk::ct_win);
oid_modify_attr(oid_root($ct_doc),"dock","top");
There may be complications with this approach if you have multiple documents open at the same time--I haven't tried that so I don't know for sure.
--Clay
