Hosted by
|
What's new
- 1 June 2007
-
The new release candidates for OWLNext and OCFNext,
owl 6.20rc17,
ocf 6.20rc17 and
owlbcb 6.20rc17
are available.
Changes include several fixes submitted by Frank Rast, Luigi Bianchi, Andrew Bond.
Pre-build libraries for several compilers are available.
- 29 May 2007
-
The new release candidates for OWLNext and OCFNext,
6.20rc16,
6.20rc16
are available.
Changes include a fix for multiline edit control and a VCL-compatibility change in the makefile.
Pre-build libraries for several compilers are available.
- 17 May 2007
-
The new release candidates for OWLNext and OCFNext,
6.20rc15,
6.20rc15
are available.
Changes include a fix in TGlyphButton,
addition of TOleAutoDll class in OCFNext to allow calling SafeArrayGetVartype() from BC5.02 applications,
and several BDS2007 compatibility changes.
- 2 May 2007
-
The new release candidates for OWLNext and OCFNext,
6.20rc14,
6.20rc14
are available.
Changes include a fix for the loaded MSVC run-time libraries and some Unicode-related fixes for BDS2006/2007.
- 23 April 2007
-
The new release candidates for OWLNext and OCFNext,
6.20rc13,
6.20rc13
are available.
Changes include:
- More changes int the Document template and streaming macros to allow building with the new Borland Developer Studio
- A bug fix in OCF, which did not allow the controller examples from the tutorial to work.
The About page is updated.
- 16 April 2007
-
The new release candidates for OWLNext and OCFNext,
6.20rc12,
6.20rc12
are available.
Changes include:
- Changes to allow building with the new Borland Developer Studio
- Automatic library linking by pragma comment(lib, "owl????.lib") is enabled for
C++ Builder 6.0 and latest.
- New batch build file VCMAKE.BAT by Vidar Hasfjord for VC2003 and VC2005.
- A fix for an issue with the Printing Dialog called before the main TApplication object is initialized
- 31 March 2007
-
The new release candidate for OWLNext,
6.20rc11 is available.
Changes include:
- Bugfixes submitted since rc10:
- Updated batch build files for VC6, VC2003, VC2005.
The new files are msc6owl.bat, msc7owl.bat, msc8owl.bat,
msc6ocf.bat, msc7ocf.bat, msc8ocf.bat.
If the corresponding version Visual Studio is installed in it's default location under
C:\Program Files\, the batch file simply needsto be run.
If the Visual Studio is not installed in it's default location, then an environment variable named
VS6ROOT, VS7ROOT or VS8ROOT
needs to be set before running the batch file.
The new release candidate for OCFNext,
6.20rc11 is available.
Changes include:
- Changes submitted by Armin Tueting
- Changes submitted by Mohsen Jahanshahi for compatibility with his Ole GenPro tool
- As a result from these changes, a problem occured with building OCF Automation application
with Borland C++ 5:
Line AUTOFUNC0 (NewDoc, OpenDoc, TAutoObject<TDrawDocument>, ) causes
Error: step18.h(42,3):Ambiguity between 'TAutoVal::operator =(void *)' and 'TAutoVal::operator =(TObjectDescriptor)'
To resolve the problem, I introduced new set of automation macros to be used when the return value is
TAutoObject - AUTOFUNC0O, AUTOFUNC1O, etc. The line above can be replaced with:
AUTOFUNC0O (NewDoc, OpenDoc, TDrawDocument, )
- This last OCFNext releease still has some issues, not all examples are working perfectly, so don't
use it for production builds.
- 4 March 2007
- As you can see, the site has new design.
Most of the pages are not yet updated to the new look, and the old site is
still available here, but not all internal links may work.
- 4 March 2007
- The new release candidate,
6.20rc10 is available.
Changes include:
- The printing module uses by default the new Print Dialog Box. This can be turned off
by setting to false the flag UseOldDialog in TPrintDialog::TData structure.
- A fix which prevented diagnostic build from working.
- A fix
in TLayoutWindow destructor.
- 12 June 2006
- The new release candidate,
6.20rc9 is available.
After version 6.20 is finalized, the work for removing the 16-bit support will begin.
There is also a release candidate for OCFNext, it is versioned
6.20rc9, to be in sync with OWLNext,
although there were no OCFNext 6.20rc1-rc6,rc8.
- 9 March 2006
- There is a proposal to remove the 16-bit support
in the source code of OWLNext in order to clean the code base and optimize several function calls.
If anyone is still interested in using a 16-bit version of OWLNext, please post to the
mailing list
|
