DeskSpace Released

DeskSpace has been released. This version fixes a number of minor bugs.

DeskSpace contains the following new features and bug fixes:

  • Bug Fix – Fixed a problem on multi-monitor systems where a small rectangle would appear after one of the monitors turned off.
  • Bug Fix – The mouse no longer freezes for 3 seconds when changing taskbar or Start Menu settings.
  • Bug Fix – Fixed a delay and potential lockup when modifying taskbar buttons during a desktop switch.
  • Bug Fix – DeskSpace no longer incorrectly determines that Windows DeskScapes is running.
  • Bug Fix – Applications (e.g. Outlook) no longer incorrectly move between desktops.
  • Bug Fix – Added a workaround for a video driver bug to prevent texture corruption on nVidia video cards at resolutions with 1050 and 1366 pixel widths.
  • Bug Fix – Fixed a bug where opening a file in Explorer would move the application that handled that file type to the current desktop. DeskSpace now keeps the application on its original desktop and optionally displays an “application attention” message.

You can visit the DeskSpace page to find out more about DeskSpace, and visit the Online Store to buy DeskSpace

3 Responses to “DeskSpace Released”

  1. ubuntu user says:

    Was ready to purchase, but its a memory hog. 130MB! you can do better…

  2. I’m sure we can shave off a MB or two from parts of the code, but the majority of the 130MB is used by the desktop textures shown on each cube face. Future versions will allow you to reduce memory usage by decreasing the quality of these textures, much like games have “high quality” and “low quality” modes.

    Please note that Windows and Linux (and Mac OS X) will all use the same amount of memory to achieve these kinds of effects, it’s just that they report memory usage differently. For example, under Vista the DWM.EXE system process allocates all memory for the Vista thumbnail and Flip effects, so 3rd party applications that use these effects will look like they’re only using a few MB when viewed in the task manager, when in fact they could be using 100′s of MB (with memory usage split between themselves and the DWM.EXE system process).

    Under Ubuntu with Compiz installed, you’ll find that memory usage is split between the “compiz.real” process and the “X” process. You’ll also find that Compiz can use far more than 130MB ;)