mirror of
https://github.com/fadden/ciderpress.git
synced 2024-06-01 07:41:58 +00:00
250d1043e3
The original version of CiderPress used a WinHelp help file, built with an application called HelpMatic Pro. This app used a proprietary format, and had no facility for exporting to "raw" HPJ + RTF files, so I decompiled the HLP and imported it into HelpScribble. Using HelpScribble, I cleaned up the help file formatting a little, fixed up the table of contents, and exported as "raw" HtmlHelp (HHP, HHK, HHC, and a whole bunch of HTML). I also split the pop-up help text, which isn't supported by HelpScribble, into a separate text file that Microsoft's HTML Help Workshop understands. I'm checking in the files that HTML Help Workshop needs to generate a CHM, so anyone can update the help text. I'm also checking in the CHM file, rather than adding the help workshop to the build, so that it's not necessary to download and configure the help workshop to build CiderPress. This change adds all of the updated help, but only updates the Help and question mark button actions for one specific dialog. A subsequent change will update the rest of the dialogs. This change is essentially upgrading us from a totally obsolete help system to a nearly-obsolete help system, but the systems are similar enough to make this a useful half-step on the way to something else. The code will centralize help activation in a pair of functions in the main app class, so any future improvements should be more limited in scope. This also adds a build step to copy the CHM to the execution directory.
34 lines
4.2 KiB
HTML
34 lines
4.2 KiB
HTML
<HTML><HEAD>
|
|
|
|
<TITLE>Preferences - Disk Image</TITLE>
|
|
<OBJECT TYPE="application/x-oleobject" CLASSID="clsid:1e2a7bd0-dab9-11d0-b93a-00c04fc99f9e">
|
|
<PARAM NAME="Keyword" VALUE="disk">
|
|
<PARAM NAME="Keyword" VALUE="image">
|
|
<PARAM NAME="Keyword" VALUE="preferences">
|
|
</OBJECT>
|
|
<META NAME="AUTHOR" CONTENT="Copyright (C) 2014 by CiderPress authors">
|
|
<META NAME="GENERATOR" CONTENT="HelpScribble 7.8.8">
|
|
<STYLE> span { display: inline-block; }</STYLE>
|
|
</HEAD>
|
|
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#800080" ALINK="#FF0000">
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="4">Disk Image Preferences</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2">You can access the Disk Image Preferences by selecting "Preferences..." from the "Edit" menu, and then clicking on the "Disk Images" tab.</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="3"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="3"><B>General</B></FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2">If "confirm disk image format" is enabled, you will be shown the <A HREF="t20.htm">Disk Image Characteristics</A> dialog whenever a disk image is opened. This gives you an opportunity to see what format CiderPress believes the disk is in, and to override it.</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2">The "default to read-only when opening volumes" setting determines whether the "read-only" box is checked in the Open Volume dialog. This should normally be set as a safety feature, but if you find yourself writing to physical disks frequently, you can save yourself a click by disabling this option.</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2">"Allow write access to physical disk 0" disabled a safety feature. On most systems, physical disk 0 is your boot disk (i.e. C:\). If you have multiple drives, this may not be the case. By default, CiderPress prevents you from opening physical disk 0 for writing; if you set this checkbox, write access will be allowed. It's best to leave this disabled unless you get a message that says, "Unable to open '80:\': for safety, write access to this volume is forbidden" while trying to open a disk that you are sure contains Apple II data.</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="3"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="3"><B>ProDOS</B></FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2">When Apple released GS/OS, they added the ability to have lower-case letters and spaces in file and volume names. This made file listings nicer to look at, but broke compatibility with versions of ProDOS 8 older than v1.8. If "allow lower-case letters and spaces in filenames" is enabled, files added to ProDOS disks will use mixed-case filenames. If disabled, all filenames are stored in upper case. Uncheck this item for best compatibility.</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2">The "use 'sparse' allocation for empty blocks" option enables a handy space-saving feature. Disk blocks filled entirely with zeroes aren't actually written to disk. Every version of ProDOS supports this feature, so there's no real reason to disable it, but it's there if you want to experiment.</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;">
|
|
</P>
|
|
</BODY></HTML>
|