The diskimg and nufxlib libraries still work with narrow-string filenames. The new release uses UNICODE, which meant changing a lot of code to use wide-character UTF-16 strings for the UI and filenames. Use of the older ANSI / Multi-Byte Character Set APIs are discouraged in favor of the UNICODE / wide-character APIs.ĬiderPress v3.x used MBCS. When you call SomeFunction, a header file remaps it to SomeFunctionA or SomeFunctionW, depending on whether you have "MBCS" or "UNICODE" defined. If WinXP ceases to be interesting, we can shave a few MB off the size of the installer. Because of the popularity of WinXP, I went ahead and made these changes. This was annoying, so now the CiderPress project includes source code snapshots, and just builds them from scratch.īuilding for WinXP in Visual Studio 2013 requires selecting a WinXP-compatibility Platform Toolset, and including a couple of hefty redistributable libraries in the install package. In the past, NufxLib and zlib were built externally, and included as pre-built libraries. The automatic conversion of the project files left a bit to be desired, but I think I've hammered out most of the weirdness. This required a pretty significant revamp of the project/solution files, and I took the opportunity to rearrange the output directory layout a bit. My goal is to keep CiderPress going for another 10 years, so I updated everything to work with Visual Studio 2013. Getting VS6 installed on Windows 7 was something of an exercise, and I don't expect that to get easier. The current-user entries take priority over the local-machine entries, so it generally works, but it may fail to recognize a previous entry that only exists in the local-machine part of the registry.ĬiderPress 3.x required Visual Studio 6, which was released in 1998.
So I'm keeping the file type association code in CiderPress, but now it only affects the current user rather than all users on the machine. The DeployMaster-based installer currently has a UI limitation that prevents it from showing all 18 file types that CiderPress handles, which means it may not give you an opportunity to prevent CiderPress from taking charge of a file extension.
The correct way to deal with this is to let the installer set and clear the associations, and use the Windows control panel to make any changes. This caused the code that handled file type associations by manipulating HKEY_CLASSES_ROOT to break. In recent versions of Windows, the registry keys for the machine have tighter access controls than the keys for the current user. You've probably seen installers that ask whether you want to install for all users or the current user. (3) File type associations fixed, sort of It appears that HtmlHelp is on its way out, so this is probably just kicking the can a bit farther down the road, but converting the help file from a proprietary format to HTML is a useful first step. The HTML sources are now checked into the source tree. I decompiled the WinHelp output file and used HelpScribble to convert it to HtmlHelp. To complicate matters further, the help file was developed with HelpMatic Pro, which used a proprietary format and didn't provide a way to get at the "raw" help data. The most significant impact of all this is that the Accept button in the Add Files dialog should no longer go AWOL.ĬiderPress used WinHelp, but recent versions of Windows dropped the WinHelp viewer, requiring a separate download. It would be more visually appealing if all the dialogs looked the same, but vista-style dialogs don't exist on WinXP.
Other file selection dialogs, such as for opening an archive, use the current "vista-style" dialogs. The previous release of CiderPress used "old-style" dialogs, the new release uses "explorer-style" dialogs. Selecting a collection of both files and folders is still very difficult. With Vista it even gained a standard dialog for selecting a folder. Windows has standard dialogs for selecting files. This is still a work in progress, but it seems stable and offers some usability improvements over 3.x, so I'm releasing it as a "development" version (4.0.0d1) for people to play with.Ī summary of changes, starting with the user-visible stuff: It now requires WinXP or later - Win98/ME/2K will not work - so I've bumped to the next major version, v4.0.0. The updates to CiderPress were more significant. The updates to NuLib2 were fairly minor - some changes to the build and config scripts, mostly to get it to work with Visual Studio 2013, and a few tweaks. CiderPress has a new github-hosted domain,, and its sources are at. After several years of quiet bit-rot, CiderPress and NuLib2 have received a new coat of paint.īoth projects are now in git repositories on, migrated from their CVS repositories on.
0 kommentar(er)
