* The transition from v1.1 to v1.2 was rather painless...all I needed
to do was change some module names in my code (Controllers->Services,
Conv->Strings, Dialog->Dates)
* This version implements a feature which I've been waiting for, yet
nowhere is it mentioned in the release notes or advertising -- you
can now copy and paste an Oberon/F view into another Windows
application "as a picture". Oberon Microsystems has been advertising
that you can do this via OLE, but I really have no interest in doing
this...
* Another improvement which doesn't get much mention is that when
interfacing with foreign language routines, you can now specify
aliases for the module and procedure names. This is a useful feature
(well - for me it is).
* When creating your own standalone, unlinked application, you now
have to add the contents of "Ole/Code" to your folder. This is not
mentioned in the new Users Guide.
* This version carries over a behavior of v1.1 that I didn't like --
when my code opens a new view and gives a size preference, the
framework ignores this preference if the size is greater than 4" by
6". Instead, it opens a 4" by 6" window and adds scroll bars. Since
I have a nice large monitor, this "feature" is quite annoying...does
anyone know of a workaround so that I don't have to manually resize
the windows after they're opened?
* This version carries over another behavior of v1.1 that I haven't
figured out a workaround yet -- when I create my own standalone,
unlinked application, I rename OberonF.exe to my own application name
like the documentation says. However, when I launch this new
application, the status line in the lower left corner shows my
application's name PLUS the Oberon/F version number "1.2"! Does
anyone know how to turn this off or change the version number?
* When I double click on an ".odc" file in Windows 95, it launches
OberonF like usual, but it no longer opens & displays the file.
Didn't v1.1 open & display the file?
Well, that's all the comments I have for now...not bad for 3 hours
of use... ;-)
-- Marc Martin, marc.martin@msd.ds.boeing.com