Project file is removed from workspace by SE

[rsadeh]

Hi everyone,
I'm using SlickEdit 15.0.1.3 on Fedora 12.
I and another colleague of mine (who's using Ubuntu 10.10) are experiencing a severe problem.
Quite frequently SE will remove a project file from the workspace without being requested to do so.
Since this is a linux kernel project file this results in a very long time of SE being un-responsive while it removes the kernel tags and of course if I add the project again then I need to bare again the very long time that it takes to tag the kernel.
Again, since this happens quite often it degrades our productivity.
Any idea what might cause this problem and/or how to solve it?

Thanks,
Ro'ee S.

[Graeme]

If you have maintenance and support you should go to SE support about it.

I'm wondering how two people could get a repeatable problem which presumably most people aren't getting.  

How long have you been getting this problem?

Has this problem occurred ever since you started using 15.0.1?

Did you both get the problem at the same time?

Do you have anyone else working on the Linux kernel that isn't getting this problem?

I guess it's possible your state file (vslick.stu) has been corrupted.  There's an easy way to find out.  Run slickedit with a brand new configuration folder  - when you invoke slick, use the -sc switch
vs.exe -sc some-new-empty-folder
Slick will create a virgin configuration folder.  At some stage you could import your configuration settings from your other configuration folder but perhaps to start with, just see if the project file problem has gone.  If the problem is gone, maybe you could revert to your original configuration folder, but first, with slick closed, backup the whole folder then delete vslick.stu (and maybe vrestore.slk).

You could also try to do some debugging yourself if you're keen.  On the slick command line, type fp workspace_remove and add the debug code you see below to the start of the function.  It will prompt you whether you want to remove a file from the workspace.  Similarly with _WorkspaceRemove_ProjectFile, add the debug code below.  It night give you the chance to block the removal of the project from the workspace as well as see what is initiating the removal of the project.  If you look through the code in the workspace_remove function, you'll see where it updates the tag file.  You could add some say("got here"); calls to the code to see if it's actually executing that code when the problem happens.

Edit  Forgot to say that if you change the code in wkspace.e you need to reload wkspace.e using the reload command on the macro menu.  Also it's a good idea to have backup history enabled so  you can see what you changed and revert to the original version any time.

Code: [Select]


_command int workspace_remove(_str Filename='',_str NewActiveProject='',boolean doUpdateToolbarWorkspaceList=true) name_info(','VSARG2_REQUIRES_PROJECT_SUPPORT)
{

   int asknow = _message_box(nls("Remove project %s1 from workspace %s2?",Filename,_workspace_filename),"",MB_OKCANCEL);
   if (asknow != IDYES) {
      _StackDump();
      return 1;
   }

...
}


int _WorkspaceRemove_ProjectFile(int handle,_str RelProjectFile)
{

   int asknow = _message_box(nls("Remove project %s1 from workspace %s2?",RelProjectFile,_workspace_filename),"",MB_OKCANCEL);
   if (asknow != IDYES) {
      _StackDump();
      return 1;
   }

...

}

Graeme