4
I Use This!
Activity Not Available

News

Analyzed about 1 year ago. based on code collected over 1 year ago.
Posted over 8 years ago by Vidar Hasfjord
A couple of bugs have been fixed in this release. For details, see milestone 6.34.11 in the bug tracker. OWLNext 6.42.8 (changes | code) OWLNext 6.34.11 (changes | code) Installation Guide PS. Take part in our Usage Survey.
Posted over 8 years ago by Vidar Hasfjord
Do you use 32-bit or 64-bit OWLNext? Vote in our poll by visiting the following link: http://vote.pollcode.com/38128881 It is just a simple click of the mouse. You can also leave a comment if you will, either at the poll site or here below. If you ... [More] haven't already done so, you may also want to vote in our earlier poll asking which OWLNext version you use. http://poll.pollcode.com/16863261 To learn more about 64-bit support in OWLNext, see 64-bit OWLNext. [Less]
Posted over 8 years ago by Vidar Hasfjord
A couple of bugs have been fixed in this release. For details, see milestone 6.42.7 in the bug tracker. OWLNext 6.42.7 (changes | code) OWLNext 6.34.10 (changes | code) Installation Guide PS. If you haven't already done so, tell us which version ... [More] of OWLNext you use. It wont take you any time at all. It is a simple click of the mouse in our Usage Survey. [Less]
Posted over 8 years ago by Vidar Hasfjord
Support for the newly released Embarcadero RAD Studio 10.1 Berlin has been added in these minor updates. OWLNext 6.42.6 (changes | code) OWLNext 6.34.9 (changes | code) Installation Guide PS. If you haven't already done so, tell us which version ... [More] of OWLNext you use. It wont take you any time at all. It is a simple click of the mouse in our Usage Survey. [Less]
Posted about 9 years ago by Vidar Hasfjord
These updates fix a few bugs. OWLNext 6.42.5 (changes | code) OWLNext 6.34.8 (changes | code) Installation Guide PS. If you haven't already done so, tell us which version of OWLNext you use. It wont take you any time at all. It is a simple click of the mouse in our Usage Survey.
Posted about 9 years ago by Vidar Hasfjord
These updates fix a few bugs. OWLNext 6.42.5 (changes | code) OWLNext 6.34.8 (changes | code) Installation Guide PS. If you haven't already done so, tell us which version of OWLNext you use. It wont take you any time at all. It is a simple click of the mouse in our Usage Survey.
Posted over 9 years ago by Vidar Hasfjord
This update fixes the dangling console windows. It also has some minor tweaks to the Build Output window. Go to Files to download.
Posted over 9 years ago by Vidar Hasfjord
This update fixes the dangling console windows. It also has some minor tweaks to the Build Output window. Go to Files to download.
Posted over 9 years ago by Vidar Hasfjord
These updates add support for the newly released Embarcadero RAD Studio 10 Seattle. Version 6.42.3 also fixes a bug that caused sporadic crashes, and version 6.34.7 fixes a problem building CoolPrj with Visual Studio 2015. The OWLNext library naming ... [More] convention has been updated. The compiler version number used within the library name is now based on the true version number of the compiler. For example, "owl-6.42-b710-x86-t.lib" is compiled by BCC32 version 7.10 (__BORLANDC__ == 0x710). Also, we now use prefix "c" to denote the Clang-based compilers from Embarcadero (BCC32C, BCC64). For example, "owl-6.42-c710-x86-t.lib" is compiled by the new 32-bit compiler BCC32C, and "owl-6.42-c710-x64-t.lib" is compiled by BCC64. The prefix and version number used for older compilers remain unchanged. OWLNext 6.42.3 (changes | code) OWLNext 6.34.7 (changes | code) Installation Guide PS. If you haven't already done so, tell us which version of OWLNext you use. It wont take you any time at all. It is a simple click of the mouse in our Usage Survey. [Less]
Posted over 9 years ago by Vidar Hasfjord
These updates add support for the newly released Embarcadero RAD Studio 10 Seattle. Version 6.42.3 also fixes a bug that caused sporadic crashes, and version 6.34.7 fixes a problem building CoolPrj with Visual Studio 2015. The OWLNext library naming ... [More] convention has been updated. The compiler version number used within the library name is now based on the true version number of the compiler. For example, "owl-6.42-b710-x86-t.lib" is compiled by BCC32 version 7.10 (__BORLANDC__ == 0x710). Also, we now use prefix "c" to denote the Clang-based compilers from Embarcadero (BCC32C, BCC64). For example, "owl-6.42-c710-x86-t.lib" is compiled by the new 32-bit compiler BCC32C, and "owl-6.42-c710-x64-t.lib" is compiled by BCC64. The prefix and version number used for older compilers remain unchanged. OWLNext 6.42.3 (changes | code) OWLNext 6.34.7 (changes | code) Installation Guide PS. If you haven't already done so, tell us which version of OWLNext you use. It wont take you any time at all. It is a simple click of the mouse in our Usage Survey. [Less]