Security Spy 4.0 minor issue

roadfun
edited June 2016 in SecuritySpy
First off, this is a very nice update! I always feel better seeing an update and, yes, paying something for it. I like feeling like I am contributing to ongoing support and development. The below are very minor setup items, not sure if anyone else will even run into them.

I was very happy to see scheduling made it in so I no longer have to use my launchctl scheduling trick. In setting up I did notice a snafu with setting a motion capture schedule. Initially I went to the Schedule tab, created a schedule, called it "Motion Capture", then went to the Motion tab of each camera and picked that schedule. But when I clicked back over instead of that being the setting it was instead "Manual capture" for each of my cameras. This was true even if I closed and reopened the Preferences window. I tried changing it a couple of times and always got the same result.

On a whim I decided to change the name of the schedule to "Motion Capture Schedule" in the Schedule tab then went back through each camera. For each camera I clicked on the camera name, picked that schedule, then clicked the "General" tab, then closed preferences (and it asked me to Save when I did that) and the setting stuck. I don't think changing the schedule name resulted in success, likely there is a glitch the schedule not being saved correctly depending on how you go about setting preferences. It has stuck across open/close of SS so I think I'm all set on this now.

I also noticed one other preference type glitch. In the new cameras window, which I love, I had asked it to display a couple of additional columns, which it did. But after that when I quit SS and then opened it again the columns were back to default. I picked the ones I wanted again, quit SS, and re-opened it and my choices stuck. So this is an even more minor thing.

Comments

  • Thanks for upgrading, and thanks for the very helpful feedback!

    Sorry about these minor issues, neither of these came up in our extensive testing, but they do sound like they could be bugs. We'll investigate thoroughly and hope to get them fixed for the next minor update.