Author Topic: Slick stack  (Read 1806 times)

jporkka

  • Senior Community Member
  • Posts: 136
  • Hero Points: 6
Slick stack
« on: August 11, 2008, 12:03:56 am »
During adding a project to a workspace, I hit ctrl-alt-shift-f2 to abort (added the wrong project....reallly big project).
Then I closed the workspace properties window.
Then I opended it again...it showed that project in the workspace so I removed it.
Then I hit OK and got this.

 Invalid argument
tagform.ex 1921 RetagFilesInTagFile2(D:\SlickTagFiles\Slick\E CatEnh.vtg,219,278,0,0,0,0,0,0,0,0,1,0,0,0)   p_window_id: 278   p_object: OI_EDITOR   p_name:
tagform.ex 7688 _workspace_update_files_retag(0,0,0,0,0,0,0,0,0)   p_window_id: 142   p_object: OI_EDITOR   p_name:
wkspace.ex 7896 workspace_insert(,0,0,1)   p_window_id: 142   p_object: OI_EDITOR   p_name:
wkspace.ex 38191 _workspace_properties_form.ctladd.\x{2946}()   p_window_id: 142   p_object: OI_EDITOR   p_name:
dlgeditv.ex 7407 show(-modal _workspace_properties_form)   p_window_id: 142   p_object: OI_EDITOR   p_name:
wkspace.ex 9425 workspace_properties()   p_window_id: 142   p_object: OI_EDITOR   p_name:


Slick 13.0.1 on Windows Vista.

Graeme

  • Senior Community Member
  • Posts: 1989
  • Hero Points: 228
Re: Slick stack
« Reply #1 on: August 11, 2008, 01:16:11 am »
Ctrl Alt Shift F2 isn't supposed to be used for that kind of thing and is likely to leave the runtime environment in an inconsistent and possibly unusable state.  It's not reasonable to expect all slick operations to handle "unexpected interruption" the way the NTFS file system does, for example.  If you want to use Ctrl Alt Shift F2 for that, you should backup your config folder every time you start slick and backup workspace and project files every time you open them, and also select slick to prompt for configuration save on exit. 

Graeme