4
I Use This!
Activity Not Available

News

Analyzed 4 months ago. based on code collected 7 months ago.
Posted about 3 years ago by Vidar Hasfjord
For OWLNext users writing applications that need to work with the Unicode character set, and would prefer to work with UTF-8, which has become the de-facto standard in many areas, such as text processing, communication and networking applications ... [More] , there is now good news! Well, actually, it is old news by now, but I think it is still important enough to make a news post about it. Anyway, since Windows 10 version 1903 (May 2019 Update), you can now activate an ANSI code page for UTF-8, allowing you to use narrow Unicode strings encoded in UTF-8 with the Windows API. In other words, you can continue to use the good old ANSI build mode and narrow strings for your legacy OWLNext applications and still enable full support for Unicode. For more information, see "OWLNext and Unicode". PS. For those of you who already deal with wide UTF-16 strings, see "Strings and OWLNext" for some tips on converting between narrow and wide strings. We have some upcoming additions that should help in this area. [Less]
Posted about 3 years ago by Vidar Hasfjord
For OWLNext users writing applications that need to work with the Unicode character set, and would prefer to work with UTF-8, which has become the de-facto standard in many areas, such as text processing, communication and networking applications ... [More] , there is now good news! Well, actually, it is old news by now, but I think it is still important enough to make a news post about it. Anyway, since Windows 10 version 1903 (May 2019 Update), you can now activate an ANSI code page for UTF-8, allowing you to use narrow Unicode strings encoded in UTF-8 with the Windows API. In other words, you can continue to use the good old ANSI build mode and narrow strings for your legacy OWLNext applications and still enable full support for Unicode. This should make it a whole lot easier to port OWL applications to OWLNext and Unicode. For more information, see "OWLNext and Unicode". PS. For those of you who already deal with wide UTF-16 strings, see "Strings and OWLNext" for some tips on converting between narrow and wide strings. We have some upcoming additions that should help in this area. [Less]
Posted about 3 years ago by Vidar Hasfjord
These maintenance updates address a bug in OCFNext, while providing a few OCF-related enhancements as well. The updates are released alongside the latest version of GenPro by Mohsen Jahanshahi, his tool for for generating OCF proxy source and header ... [More] files, useful for COM automation. You can read more about the latest version of this utility in our forum [discussion:7a94e7e51f]. User feedback is welcomed! OWLNext 7.0.4 (changes | code | log) OWLNext 6.44.14 (changes | code | log) OWLNext Installation Guide GenPro download [Less]
Posted about 3 years ago by Vidar Hasfjord
This update adds Help buttons to the OWLMaker Wizard pages and the dialog box for resource bitmap extraction. The help buttons are linked to the relevant sections of the OWLMaker documentation. This update also fixes a couple of minor presentational ... [More] issues in the wizard pages, and adds special handling for symbolic links (a simple symbolic link used as the toolset root will no longer be converted to canonical form, as to support workarounds for issues with long paths and paths with spaces). For more details on the changes to the OWLMaker source code, see the code log. To update an existing installation go to "Help | Check for updates" on the main menu in OWLMaker. Or use the button below to download the latest archive. See the OWLMaker documentation for installation and usage instructions. [Less]
Posted about 3 years ago by Vidar Hasfjord
This update adds Help buttons to the OWLMaker Wizard pages and the dialog box for resource bitmap extraction. The help buttons are linked to the relevant sections of the OWLMaker documentation. This update also fixes a couple of minor presentational ... [More] issues in the wizard pages, and adds special handling for symbolic links (a simple symbolic link used as the toolset root will no longer be converted to canonical form, as to support workarounds for issues with long paths and paths with spaces). For more details on the changes to the OWLMaker source code, see the code log. To update an existing installation go to "Help | Check for updates" on the main menu in OWLMaker. Or use the button below to download the latest archive. See the OWLMaker documentation for installation and usage instructions. [Less]
Posted over 3 years ago by Ognyan Chernokozhev
A new in-depth mini-article about the CVT1100 duplicate resource linker error : https://sourceforge.net/p/owlnext/wiki/CVT1100%20Error/
Posted over 3 years ago by Vidar Hasfjord
These maintenance updates fix a couple of minor issues (see [bugs:#482] and [bugs:#484]). OWLNext 7.0.3 (changes | code | log) OWLNext 6.44.13 (changes | code | log) OWLNext Installation Guide
Posted over 3 years ago by Vidar Hasfjord
These maintenance updates fix some bugs. In particular, the 7.0.2 update fixes a regression in 7.0 causing child windows to be leaked [bugs:#475]. So if you use version 7, you really should update to 7.0.2. In addition, a number of minor bugs have ... [More] been fixed in both version 6 and 7 branches. See the links below for details. OWLNext 7.0.2 (changes | code | log) OWLNext 6.44.12 (changes | code | log) OWLNext Installation Guide [Less]
Posted over 3 years ago by Vidar Hasfjord
This update is a fresh compilation of the latest source code against the latest state of the OWLNext trunk (version 7.1) and thereby fixes some bugs (with dragging the toolbar, in particular — see [bugs:#480]). For more details on the changes to the OWLMaker source code, see the code log.
Posted over 3 years ago by Vidar Hasfjord
This update is a fresh compilation of the latest source code against the latest state of the OWLNext trunk (version 7.1) and thereby fixes some bugs (with dragging the toolbar, in particular — see [bugs:#480]). For more details on the changes to the OWLMaker source code, see the code log.