I created a form, and it was just a test form that I'm done with now, and I'd like to delete it (it's taking up space in the forms list and has a silly name).
My ultimate goal is to delete this junky test form that I created, but as I've been researching how to do that I ran across numerous posts saying that forms like this automatically get saved to both the .sta file and also to vusrobjs.e, and that I can delete the .sta file, delete the form from the vusrobjs.e file, and reload, which will rebuild the .sta file without the form, thus effectively deleting the form.
The problem I've run into with that is that I cannot find the vusrobjs.e file anywhere.
Where does vusrobjs.e get created? I ran a recursive where under the "c:\Program Files\SlickEdit 2007 Trial" folder, but there is no such file. I even got a recursive directory listing and sorted by date/time but only 3 files have modtimes later than August 2007: rescue.sta, vslick.sta, and vstrial.dat. I can't find the vusrobjs.e file anywhere -- is creating a form still enough to cause it to get created?
I'm also a little confused about why modified forms always go into the state file, even if the form was opened from a macro file. My natural thinking would be that even if I am customizing the editor for my own use and don't intend to publish my macros, it would still be helpful to keep my forms in source code form (if you'll pardon the two bit pun) by default so that they naturally survive corruption of the state file or upgrades or etc. Is this one of those "yeah it's been beaten to death and someday will get better" types of things (I can live with that, I'm just curious is all
, or is there a reason I'm missing that explains why it's usually advantageous for them to get saved in the state file instead?
I am a source-control-aholic and plan to keep all of my SlickEdit macros under source control, with revision history. I want to be able to reliably recreate my editor configuration whenever I want to, from sources.