Stardock Improves Object
Desktop 2.0 with NetScan

OBJECT DESKTOP 2.0 FOR OS/2
Beta 4 is Available


Object Desktop Beta 4 is now available on Stardock website. To get the update jump this URL:

http://www.stardock.com/update/update_od20.htm

Stardock announces today September 29 Object Desktop 2.0 goes to manufacturing and is showing a big screenshot in his website, at
http://www.stardock.com/
Object Desktop 2.0 for OS/2 is not a simple upgrade from the version 1.5.2 of Object Desktop Professional. It have very importants enhancements, like Object NetScan.
Updates for Object Desktop 2.0 Beta 4


Enhanced Folder

1. If Toolbar under options tab is not enabled, a toolbar
appears at the bottom of the folder

2. When navigating using the toolbar drop-down and goto
parent button, some folders would remain cross-hatched
(open emphasis).

3. When a folder is not in browse mode, the parent folder
button should open a new view.

4. Use Ctrl button to open a new view with parent button
when folder is in browse mdoe.

5. Beta 3 rendered copy/move/create toolbar buttons
unusable.

6. Add the "always use grid view" global option.


Object Navigator

1. When re-sizing an Object Navigator window horizontally
larger, small black vertical lines appear in the new window
border where the old window border was.


Master Setup

1. When shell is restarted, Control Center and other
objects were not restarted until Object Desktop folder was
opened.

2. To avoid OS/2 desktop archive problem where old Master
Setup objects would retain settings and activity, use INI
data for restart object settings.


Object Netscan

1. General problems with display when set horizontally and
1-high mode.


Virtual Desktop


1. Layout code now keeps from moving some windows which
start with NULL size (0,0) from moving off-screen.

2. WarpCenter should be automatically recognized as locked
window (SmartCenter was, WarpCenter was not).

3. When no applications were open, desktop swich would not
occur.


Window Controls

1. Rollup button of the Task Manager would corrupt winodw.


Object Package


1. On some systems with large number of classes or large
SOMIR= environment variable (eg. Smartsuite), Object
Package would fail to work for store desktop. Smaller
number of files could be stored, but large complete shell
would not.

2. Multiple open/close of object package editor would
eventually cause a message displayed for corrupt file, when
file was not actually corrupt.
@Macarlo, Inc.
@Macarlo's Shareware & Web
OS/2
Java Lobby Member
Java Site Accredited

[TOP] [HOME] [INDEX]