Author Topic: Saving the state is a hit or miss thing  (Read 717 times)

jorick

  • Senior Community Member
  • Posts: 341
  • Hero Points: 15
Saving the state is a hit or miss thing
« on: August 30, 2018, 03:06:48 pm »
There's a big problem when it comes to saving the state when exiting or switching workspaces.  Many times it doesn't work.

A couple of days ago I wanted to work on a different project so I closed my workspace and set up a new one.  Today I wanted to return to the project I was working on but when I loaded the workspace, it contained the setup and files from a month ago.

Another time I exited SE after installing a hotfix and came back in to files I haven't worked on in a long time.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 4791
  • Hero Points: 388
Re: Saving the state is a hit or miss thing
« Reply #1 on: August 30, 2018, 06:27:08 pm »
Make sure you are only running one instance of SlickEdit. Also, make sure there aren't any hidden SlickEdit processes running.

jorick

  • Senior Community Member
  • Posts: 341
  • Hero Points: 15
Re: Saving the state is a hit or miss thing
« Reply #2 on: August 31, 2018, 12:37:50 pm »
I have only one instance running.

Forgot the info.

SlickEdit Pro 2017 (v22.0.2.1 64-bit)

Serial number: [redacted]
Licensed number of users: Single user
License file: C:\ProgramData\slickedit\22\slickedit.lic

Build Date: July 12, 2018
Emulation: CodeWright

OS: Windows 7 x64
OS Version: 6.01.7601  Service Pack 1
Memory: 47% Load, 13644MB/28577MB Physical, 14531MB/57152MB Page File, 963MB/8388607MB Virtual
Shell Information: C:\Windows\system32\cmd.exe /q
Screen Size: 1680 x 1050, 1680 x 1050, 1920 x 1200, 1680 x 1050, 1680 x 1050

Project Type: (Other)
Language: .c (C/C++)
Encoding: Automatic

Installation Directory: C:\Program Files\SlickEdit Pro 22.0.2\ (non-removable drive,NTFS,80427MB free)
Configuration Directory: C:\Users\rbennet\Documents\My SlickEdit Config\22.0.2\ (non-removable drive,NTFS,80427MB free)
Migrated from: C:\Users\rbennet\Documents\My SlickEdit Config\22.0.0\

Hotfixes:
C:\Users\rbennet\Documents\My SlickEdit Config\22.0.2\hotfixes\hotfix_se2202_11_cumulative.zip (Revision: 11)

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 4791
  • Hero Points: 388
Re: Saving the state is a hit or miss thing
« Reply #3 on: August 31, 2018, 03:27:51 pm »
Can you cause this to happen on demand? If so, we will probably need your .vpwhist file.

There is code which displays a message if SlickEdit is unable to save the state information.

jorick

  • Senior Community Member
  • Posts: 341
  • Hero Points: 15
Re: Saving the state is a hit or miss thing
« Reply #4 on: September 11, 2018, 02:55:43 pm »
I can't cause it to happen on demand.

Last night my computer rebooted due to Windows updates.  The open files, tool bars, and tool windows went back to a state from months ago.  Custom icons were lost. 

When Windows reboots, everything closes down gracefully as if the X was clicked, as far as I know.  So it wasn't a crash this time.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 4791
  • Hero Points: 388
Re: Saving the state is a hit or miss thing
« Reply #5 on: September 11, 2018, 03:17:48 pm »
What's the date on your vrestore.slk file? It should roughly match the time that your machine restarted. If it doesn't, then it sounds like SlickEdit never wrote the file (didn't shutdown safely or IO Error?).

jorick

  • Senior Community Member
  • Posts: 341
  • Hero Points: 15
Re: Saving the state is a hit or miss thing
« Reply #6 on: September 11, 2018, 03:32:50 pm »
I searched my entire C: drive and couldn't find a vrestore.slk file.  Where would I normally find it?

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 4791
  • Hero Points: 388
Re: Saving the state is a hit or miss thing
« Reply #7 on: September 11, 2018, 03:50:05 pm »
It would be in the version config directory

jorick

  • Senior Community Member
  • Posts: 341
  • Hero Points: 15
Re: Saving the state is a hit or miss thing
« Reply #8 on: September 11, 2018, 03:51:33 pm »
What's the path to that directory?

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 4791
  • Hero Points: 388
Re: Saving the state is a hit or miss thing
« Reply #9 on: September 11, 2018, 04:00:58 pm »
I’m not at a computer right now. Your help about info should show it.

jorick

  • Senior Community Member
  • Posts: 341
  • Hero Points: 15
Re: Saving the state is a hit or miss thing
« Reply #10 on: September 11, 2018, 06:42:10 pm »
I think I solved the problem.  I have two different SE installs, 22.0.0 and 22.0.2; and seven different configurations, 21.0.0, 21.0.1, 21.0.2, 21.0.3, 21.0.3x, 22.0.0, and 22.0.2.  There are four different launch icons.  Two are in the SE start menu (22.0.0 and 22.0.2), one in the Startup menu (22.0.0), and one in the Quick Launch bar (22.0.2).

So when the computer restarts, the executable and configuration for 22.0.0 is read.  Then if I restart SE, the executable and configuration for 22.0.2 is read.  Very confusing.  But when I launch either one, the last saved state of that install is restored, so it definitely works.

In order to save my sanity, I created a shortcut in the SE config folder that points to the most recent executable.  I then created two hard links, one in the Startup menu and one in the Quick Launch bar, that point to the shortcut in the config folder.  I left the two links under the SE menu alone since I never use them and they show which install they each go to.  Then the next time I update the program, I'll change the destination in either the shortcut or the hard links and all links get updated at the same time.

Yes, I know I should do an uninstall of the old version, but I have qualms not knowing if that will affect the most recent version.

So you can consider this matter closed.  (Unless you can figure out some way around the shortcut issue. :) )