ciderpress/.gitignore

# build product output directories (top-level and component)
Debug
Release

# precompiled headers
ipch

# binaries generated by Visual Studio
CP.sdf
CP.opensdf
CP.v12.suo
*.aps
.vs/

# installer binary
DIST/Setup*.exe

# linux binaries
*.o
diskimg/libdiskimg.a
diskimg/libhfs/libhfs.a

# ctags
tags

# VIM
*~
*.swp
Move file association handling back into the app The DeployMaster installer issue prevents the user from seeing more than nine of the 18 file extensions that CiderPress wants to handle, and I don't want to go stomping on file associations without some way to disable the behavior. So this returns to the previous behavior, where CiderPress directly manages the file associations. The CiderPress app is not able to modify HKEY_LOCAL_MACHINE (which it used to do via HKEY_CLASSES_ROOT) on recent versions of Windows -- tested in Win7, but it probably broke with Vista. So now we do everything in HKEY_CURRENT_USER. This works, more or less. We're not looking at the Windows shell overrides, which are made in yet another set of registry entries, so there are multiple reasons why the values reported by the Edit Associations dialog may now be inaccurate. I still favor eliminating the dialog as a long-term strategy. I took the opportunity to do some code cleanup in the registry code. I also added calls to SHChangeNotify() to tell the Windows shell when file associations change, so Windows Explorer windows get updated promptly. 2014-12-15 21:57:09 -08:00			`# build product output directories (top-level and component)`
Visual Studio 2013 update This updates the project files for Visual Studio 2013, and removes the old Visual Studio 6 (1998) project files. The update tool had a number of complaints (see UpgradeLog.htm) that may need to be addressed. Also, replaced .cvsignore with .gitignore. Visual Studio reports 1886 build errors, nearly all of them due to the switch from MBCS to Unicode. The former is no longer supported "out of the box", and its use is discouraged, so we're going to bite the bullet and use wide characters in the UI. 2014-11-03 14:00:35 -08:00			`Debug`
			`Release`

			`# precompiled headers`
			`ipch`

			`# binaries generated by Visual Studio`
			`CP.sdf`
			`CP.opensdf`
			`CP.v12.suo`
			`*.aps`
Half-step toward VS2015 CE When initially opened in Visual Studio 2015 Community Edition, the project was updated to use the v140_xp toolset. When the program was run under WinXP it complained about a missing runtime DLL. When the DLL was provided, it complained about another one (with a slightly strange name). So I reverted the tools to v120_xp, i.e. Visual Studio 2013. (I don't know if this works because the tools are included with VS2015, or because I have VS2013 installed and it managed to find them.) Whatever the case, it now builds for me with either IDE, and seems to work fine on Windows XP, but I'd like to figure out why the XP build isn't working with the v140_xp tools. 2016-01-11 11:27:03 -08:00			`.vs/`
Visual Studio 2013 update This updates the project files for Visual Studio 2013, and removes the old Visual Studio 6 (1998) project files. The update tool had a number of complaints (see UpgradeLog.htm) that may need to be addressed. Also, replaced .cvsignore with .gitignore. Visual Studio reports 1886 build errors, nearly all of them due to the switch from MBCS to Unicode. The former is no longer supported "out of the box", and its use is discouraged, so we're going to bite the bullet and use wide characters in the UI. 2014-11-03 14:00:35 -08:00
Move file association handling back into the app The DeployMaster installer issue prevents the user from seeing more than nine of the 18 file extensions that CiderPress wants to handle, and I don't want to go stomping on file associations without some way to disable the behavior. So this returns to the previous behavior, where CiderPress directly manages the file associations. The CiderPress app is not able to modify HKEY_LOCAL_MACHINE (which it used to do via HKEY_CLASSES_ROOT) on recent versions of Windows -- tested in Win7, but it probably broke with Vista. So now we do everything in HKEY_CURRENT_USER. This works, more or less. We're not looking at the Windows shell overrides, which are made in yet another set of registry entries, so there are multiple reasons why the values reported by the Edit Associations dialog may now be inaccurate. I still favor eliminating the dialog as a long-term strategy. I took the opportunity to do some code cleanup in the registry code. I also added calls to SHChangeNotify() to tell the Windows shell when file associations change, so Windows Explorer windows get updated promptly. 2014-12-15 21:57:09 -08:00			`# installer binary`
			`DIST/Setup*.exe`

gcc/linux updates Many updates to format strings, largely as a result of changing various "long" variables to uint32_t. Fixed the diskimg debug macros for gcc, which requires an extra "##" to remove the "," when there are no arguments. (Apparently Visual Studio just strips this away for you.) Stripped out a couple of dead variables spotted by gcc. Return the actual error in a couple of HFS file functions. 2014-12-11 16:04:35 -08:00			`# linux binaries`
			`*.o`
			`diskimg/libdiskimg.a`
			`diskimg/libhfs/libhfs.a`

			`# ctags`
			`tags`

Move file association handling back into the app The DeployMaster installer issue prevents the user from seeing more than nine of the 18 file extensions that CiderPress wants to handle, and I don't want to go stomping on file associations without some way to disable the behavior. So this returns to the previous behavior, where CiderPress directly manages the file associations. The CiderPress app is not able to modify HKEY_LOCAL_MACHINE (which it used to do via HKEY_CLASSES_ROOT) on recent versions of Windows -- tested in Win7, but it probably broke with Vista. So now we do everything in HKEY_CURRENT_USER. This works, more or less. We're not looking at the Windows shell overrides, which are made in yet another set of registry entries, so there are multiple reasons why the values reported by the Edit Associations dialog may now be inaccurate. I still favor eliminating the dialog as a long-term strategy. I took the opportunity to do some code cleanup in the registry code. I also added calls to SHChangeNotify() to tell the Windows shell when file associations change, so Windows Explorer windows get updated promptly. 2014-12-15 21:57:09 -08:00			`# VIM`
Visual Studio 2013 update This updates the project files for Visual Studio 2013, and removes the old Visual Studio 6 (1998) project files. The update tool had a number of complaints (see UpgradeLog.htm) that may need to be addressed. Also, replaced .cvsignore with .gitignore. Visual Studio reports 1886 build errors, nearly all of them due to the switch from MBCS to Unicode. The former is no longer supported "out of the box", and its use is discouraged, so we're going to bite the bullet and use wide characters in the UI. 2014-11-03 14:00:35 -08:00			`*~`
			`*.swp`