Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!howland.reston.ans.net!EU.net!uunet!eskimo!mlonge
From: mlonge@eskimo.com (Michael Longe)
Subject: Re: upgrade to vwin32 worthwhile?
Message-ID: <CynGwH.FGu@eskimo.com>
Organization: Eskimo North (206) For-Ever
X-Newsreader: NN version 6.5.0, beta 3, #5 (NOV)
References: <mjbCyIB7q.Kvy@netcom.com>
Date: Wed, 2 Nov 1994 17:07:21 GMT
Lines: 34

mjb@netcom.com (Martin Brown) writes:

>I contemplating upgrading to vwin32.

>How robust is vwin32?  Any glaring problems or deficiencies with this product?  

>Is this a worthwhile upgrade?

>Is this upgrade available from some mail-order place cheaper than from Digitalk?

I've been using ST/V Win32 for a few weeks now, to prototype a Mac and Windows
cross-platform product. (Obviously, PP would have been better for ST 
portability but I need to access the native features on each platform.)
Because of that, I can't use the MDI classes (which is just as well, because
there are bugs in the "MDI Mode" of the development environment).

Other than trying to sort out what is possible to do on both platforms with
the same source, the Win32 version seems okay, and the event mechanism makes it
easier to divide view and model than Win16. Running under Win32s, however, I've
seen a number of system crashes, including a "memory parity error" lockup
that I'm a little suspicious of. I tend to blame MicroSlop for Win32s-related
problems in most cases.

I don't know that any of the catalogs have the Win16->Win32 upgrade, but the
upgrade is definitely cheaper than buying the Win32 version separately.


Michael Longe'
Designer Software  P.O. Box 4502  Federal Way, WA 98063  206-946-5218
mlonge@eskimo.com
-- 
Michael Longe'
Designer Software  P.O. Box 4502  Federal Way, WA 98063  206-946-5218
mlonge@eskimo.com
