July 23rd, 2008
It’s been a month since we released Slife 2.0. Today we have an update, Slife v2.0.1, that addresses a number of issues in the v2.0 that came up in the forum and in our own tests. Here’s the list of changes:
- Added label to side panel
- Removed activities from side panel
- Improved search performance
- Optimized performance of all visualizations
- Fixed drawing bug in Month view
- Fixed scrolling bug in Applications, Web & Documents and Activities view
- Fixed selection/highlight bug in Activities view
- Displaying icons correctly for Microsoft Office 2004/2008 applications
- Displaying icons correctly for Adobe CS3 applications
- Displaying icon correctly for iWork’s Numbers
- Replaced Activity Editor window with an inspector-type window
- Added File menu, removed Activity menu from menu bar
- Fixed bug that prevented Activities from saving when app quit
- Added ability to delete apps from application tracking list
You can download Slife v2.0.1 here. We will be updating the link in the download page and releasing it through auto-update for everyone later this week.
Over the next few weeks we will be working on some of the excellent, but more substancial feature suggestions. Stay close!
This entry was posted
on Wednesday, July 23rd, 2008 at 6:40 am and is filed under News, Slife.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
January 12th, 2009 at 4:18 am
Hello Slife team,
For some reason, Slife refuses to run in the background when opened as a login item. On Mac OS X 10.5, I added Slife to the “Open at Login” elements, and checked the “Hide” option in System Prefs, Accounts, Login items. The box systematically unchecks, and Slife systematically adds to window clutter at login.
Is this the result of bad parameter-setting on my side, of a bug, or of deliberate programming? I like to load stuff like Stickies or Slife straight from session start, but I do not want to have them show up on screen.
January 15th, 2009 at 7:04 am
Hi – Yes, we are aware of this issue and hope to have it fixed soon!