{ "disks": { "1": { "dirs": [ { "path": "/", "files": [ { "name": "DISK_ID", "size": 8, "date": "1991-03-01", "time": "11:36" }, { "name": "INSTALL EXE", "size": 171463, "date": "1991-02-16", "time": "17:36" }, { "name": "INSTALL CWA", "size": 20623, "date": "1991-02-15", "time": "20:05" }, { "name": "INSTALL HLP", "size": 1346, "date": "1991-02-12", "time": "14:26" }, { "name": "README DOC", "size": 10216, "date": "1991-03-01", "time": "2:00" }, { "name": "UPGRADE DOC", "size": 11037, "date": "1991-03-01", "time": "2:00" }, { "name": "H_LIB DOC", "size": 7175, "date": "1991-03-01", "time": "2:00" }, { "name": "INSTALL CFG", "size": 6649, "date": "1991-03-01", "time": "11:52" }, { "name": "SSDATA SSC", "size": 480243, "date": "1991-03-01", "time": "11:39" } ] } ], "volume": "CW1AC2.0" }, "2": { "dirs": [ { "path": "/", "files": [ { "name": "DISK_ID", "size": 8, "date": "1991-03-01", "time": "11:39" }, { "name": "INSTALL EXE", "size": 171463, "date": "1991-02-16", "time": "17:36" }, { "name": "INSTALL CWA", "size": 20623, "date": "1991-02-15", "time": "20:05" }, { "name": "INSTALL HLP", "size": 1346, "date": "1991-02-12", "time": "14:26" }, { "name": "INSTALL CFG", "size": 17429, "date": "1991-02-25", "time": "13:49" }, { "name": "SSDATA SSC", "size": 514253, "date": "1991-03-01", "time": "11:41" } ] } ], "volume": "CW2AC2.0" }, "3": { "dirs": [ { "path": "/", "files": [ { "name": "DISK_ID", "size": 8, "date": "1991-03-01", "time": "11:41" }, { "name": "SSDATA SSC", "size": 723733, "date": "1991-03-01", "time": "11:43" } ] } ], "volume": "CW3AC2.0" }, "4": { "dirs": [ { "path": "/", "files": [ { "name": "DISK_ID", "size": 8, "date": "1991-03-01", "time": "11:43" }, { "name": "SSDATA SSC", "size": 727389, "date": "1991-03-01", "time": "11:46" } ] } ], "volume": "CW4AC2.0" }, "5": { "dirs": [ { "path": "/", "files": [ { "name": "DISK_ID", "size": 8, "date": "1991-03-01", "time": "11:46" }, { "name": "SSDATA SSC", "size": 722037, "date": "1991-03-01", "time": "11:48" } ] } ], "volume": "CW5AC2.0" }, "6": { "dirs": [ { "path": "/", "files": [ { "name": "DISK_ID", "size": 8, "date": "1991-03-01", "time": "11:49" }, { "name": "SSDATA SSC", "size": 728150, "date": "1991-03-01", "time": "11:51" } ] } ], "volume": "CW6AC2.0" }, "7": { "dirs": [ { "path": "/", "files": [ { "name": "DISK_ID", "size": 8, "date": "1991-03-01", "time": "11:51" }, { "name": "SSDATA SSC", "size": 322244, "date": "1991-03-01", "time": "11:52" } ] } ], "volume": "CW7AC2.0" }, "8": { "dirs": [ { "path": "/", "files": [ { "name": "DISK_ID", "size": 8, "date": "1991-03-01", "time": "12:04" }, { "name": "INSTALL EXE", "size": 171463, "date": "1991-02-16", "time": "17:36" }, { "name": "INSTALL CWA", "size": 20623, "date": "1991-02-15", "time": "20:05" }, { "name": "INSTALL HLP", "size": 1346, "date": "1991-02-12", "time": "14:26" }, { "name": "INSTALL CFG", "size": 17383, "date": "1991-03-01", "time": "12:10" }, { "name": "SSDATA SSC", "size": 516050, "date": "1991-03-01", "time": "12:07" } ] } ], "volume": "CW8AC2.0" }, "9": { "dirs": [ { "path": "/", "files": [ { "name": "SSDATA SSC", "size": 296033, "date": "1991-03-01", "time": "12:10" }, { "name": "DISK_ID", "size": 8, "date": "1991-03-01", "time": "12:08" } ] } ], "volume": "CW9AC2.0" } }, "desc_file": "README.DOC", "desc_text": " C-Worthy Version 2.0 Release Notes\r\n [February 26, 1991]\r\n\r\nWelcome to C-Worthy 2.0.\r\n\r\nWe're pleased that you have selected C-Worthy as your user interface\r\ndevelopment system. This version of C-Worthy owes a great deal to comments and\r\nsuggestions from C-Worthy users like yourself; if you have any problems or\r\nsuggestions for improvements we are eager to listen to you.\r\n\r\nThis file contains the latest information on this version of C-Worthy, as well\r\nas hints on solving common problems and using some of C-Worthy's features.\r\n\r\nCompiler Support Notes\r\n\r\nThese disks contain libraries to support Microsoft C versions 5.1 and 6.0,\r\nBorland Turbo C (not C++) version 2.0, and Borland Turbo C++ version 1.0.\r\n\r\nSupport for Microsoft C 5.1, Turbo C 2.0, and Turbo C++ 1.0 may not be included\r\nin future versions of C-Worthy, as these compilers have been superseded by more\r\nrecent versions.\r\n\r\nWe have not yet had the opportunity to do extensive testing with the newly\r\nreleased Borland C++ 2.0. However, source code customers will note that all\r\nthe library source code compiles correctly if the Turbo C++ 1.0 batch files are\r\nmodified to call bcc instead of tcc.\r\n\r\nUpgrade Notes\r\n\r\nSee the file \"upgrade.doc\" on the C-Worthy Install Disk if you are upgrading\r\nfrom a previous version of C-Worthy.\r\n\r\nHelp System\r\n\r\nThe file \"h_lib.doc\" on the install disk has information on how to use the help\r\nlibrarian to implement context-sensitive help.\r\n\r\nUnresolved Externals at Link Time\r\n\r\nIf, when linking, you encounter numerous errors of the form \"unresolved\r\nexternal\" or \"undefined symbol\", one of the following conditions probably\r\napplies:\r\n\r\n A. Your application has been compiled with the old versions of the\r\n C-Worthy header files. You must recompile with the new header files.\r\n\r\n If the undefined symbols are preceded by an underscore, this is the\r\n most likely source of the problem.\r\n\r\n B. Your application has been compiled without defining your compiler\r\n version on the command line. One of the following preprocessor symbols\r\n must be defined before any of the C-Worthy include files are processed:\r\n\r\n If you are using Microsoft C 6.0: MSC600 (example: cl -c -DMSC600 my.c)\r\n\r\n If you are using Microsoft C 5.1: MSC510 (example: cl -c -DMSC510 my.c)\r\n\r\n If you are using Turbo C 2.0: BTC200 (example: tcc -c -DBTC200 my.c)\r\n\r\n The best way to ensure that the correct command line options are used\r\n is to compile using the C-Worthy compiler batch files CWCL.BAT for\r\n large model and CWCM.BAT for medium model.\r\n\r\n If the undefined symbols are all capitalized, and are not preceded by\r\n an underscore, or if they are preceded by an '@', this is the most\r\n likely source of the problem.\r\n\r\n C. If your application has been compiled correctly, you could be linking\r\n with the old version of the C-Worthy libraries.\r\n\r\n_CDECL and _FASTCALL calling conventions\r\n\r\nAll C-Worthy routines are now declared as either _CDECL or _FASTCALL. These\r\nidentifiers are defined in CWGEN.H. For Microsoft C 6.0, the statements are\r\n\r\n#define _CDECL _cdecl\r\n\r\n#define _FASTCALL _fastcall\r\n\r\nFor Microsoft C 5.1 and Borland Turbo C, the statements are\r\n\r\n#define _CDECL cdecl\r\n\r\n#define _FASTCALL pascal\r\n\r\nThese statements allow C-Worthy to take advantage of special calling\r\nconventions available with these compilers, resulting in slightly smaller and\r\nfaster code. In addition, you may now use one of these calling conventions as\r\nthe default in your own program which uses C-Worthy.\r\n\r\nNote that the compiler will convert symbols declared as _pascal to all\r\nuppercase, with no prepended underscore (example: \"STRING_LENGTH\"). Symbols\r\ndefined as _fastcall will have '@' prepended by the compiler (example:\r\n\"@string_length\"), while _cdecl symbols will have a prepended '_' (example:\r\n\"_string_length\").\r\n\r\nSee \"Unresolved Externals at Link Time\" in this file for a description of\r\npossible linking problems related to these naming conventions.\r\n\r\nFor additional details, see your compiler documentation.\r\n\r\nIf you need to disable this feature (for instance, if you are recompiling\r\nC-Worthy with a compiler that does not support any of the above calling\r\nconventions), just change the lines in CWGEN.H to read\r\n\r\n#define _CDECL\r\n#define _FASTCALL\r\n\r\nNote for rebuilders of cwArchitect\r\n\r\nAs in past versions of C-Worthy, we have included library and source files to\r\nenable the intrepid customer to modify and rebuild cwArchitect to handle\r\nuser-defined data types. See the contents of the CWA directory for specifics.\r\n\r\nBecause of the greatly increased functionality of cwArchitect, it would no\r\nlonger function usefully within 640k unless we overlaid it. We selected\r\nBorland's VROOM technology to accomplish this; therefore, users who wish to\r\nrebuild cwArchitect will need to use the Turbo C++ version of the libraries for\r\nthat task, and CWA.LIB is provided only for that compiler. You may, of course,\r\ncontinue to use the modified version of cwArchitect in support of Microsoft C\r\nprogramming.\r\n\r\nAdditional toggle in cwArchitect Preferences\r\n\r\nBecause of the large amount of data associated with a menu being constructed\r\nwithin cwArchitect, cwArchitect may be unable to handle menus with very many\r\nchoices. If this occurs, cwArchitect will simply refuse to accept new menu\r\noptions in the Choices box.\r\n\r\nIf this happens to you (it should occur only with menus with very many choices,\r\nsuch as a Windows-style menu with many pulldowns), select Preferences\r\ncwArchitect from the main menu and set the Conserve Memory option to On. This\r\nwill cause cwArchitect to save menu options to disk more frequently, resulting\r\nin more capacity at the cost of slower performance.\r\n\r\nAs a side effect, with Conserve Memory on it is not possible to abandon changes\r\nmade to pulldowns by pressing Escape on the Choices box.\r\n\r\nOn-line reference for Microsoft PWB/Quickhelp\r\n\r\nThe file ISV.HLP in the C-Worthy Help directory contains the entire C-Worthy\r\nreference manual in on-line form for users of Microsoft C 6.0.\r\n\r\nCopy ISV.HLP into the directory containing your PWB help and it will be\r\ninstantly accessible from PWB or Quickhelp. To try it, type QH and the name of\r\na C-Worthy function or data type - for example,\r\n\r\n QH menu\r\n\r\nA reference page about C-Worthy's menu() function will appear.\r\n\r\nUsing the Palette Editor in your application\r\n\r\nYou may include cwArchitect's Palette Editor in your application, to allow\r\nend-users to customize screen colors.\r\n\r\nSimply call the function palette_editor() (documented in the Reference Manual)\r\nfrom the menu choice you designate.\r\n\r\nThe palette editor requires two functions in the procedure table generated by\r\ncwArchitect. The functions are:\r\n\r\n text_style_action_proc\r\n palette_display_proc\r\n\r\nTo enter the procedures, just go to any field in a cwArchitect form that\r\nrequires a procedure name (for example, the Entry Procedure field on the Form\r\nInformation form). Bring up the list of procedures by pressing , then\r\nenter the two functions by pressing and typing in their names. After you\r\nhave entered the two procedures, press Escape to leave the list without\r\nselecting a new Entry Procedure for your form.\r\n\r\nKnown Bugs\r\n\r\nThis section contains descriptions of known problems in the current version.\r\nWhere possible, we provide a workaround.\r\n\r\n Menu Choice Help Contexts may give wrong help.\r\n\r\n If you use cwArchitect to specify help contexts for menu choices, then add\r\n or delete contexts using H_LIB, you may get the wrong help for the menu\r\n choices in your application.\r\n\r\n cwArchitect normally stores the name of the context for each menu, form, or\r\n field that has a help context. In the case of menu choices, the number is\r\n stored. When help contexts are added or deleted, it is possible for some\r\n contexts to be re-numbered; therefore, stored numbers may no longer\r\n correspond to the correct help.\r\n\r\n The workaround for this version is to check your menu choice help contexts\r\n using cwArchitect after you make changes with H_LIB. If the help context\r\n that appears for the option in the Option Information box is incorrect,\r\n change it back to the correct help context.\r\n\r\n Help contexts for forms, fields, and menus work correctly.\r\n\r\n Windows-Style Menu Pulldowns don't have Destroy Objects bit set by default.\r\n\r\n If you use cwArchitect to attach an object (a menu or a form) to a pulldown\r\n choice, the memory associated with the object won't be automatically freed\r\n after you access it in your application.\r\n\r\n To automatically free the memory, read the pulldown menu in cwArchitect,\r\n select Menu Information, and set the Destroy Object bit in the Control Flags\r\n field.\r\n\r\n H_LIB Write Ascii buffer pointer off by two.\r\n\r\n The Write Ascii function of H_LIB.EXE writes two nonsense characters at the\r\n start of each help context, and truncates the last two characters of the\r\n context.\r\n\r\n This does not affect the operation of the help system, only conversion from\r\n help files to ascii files.\r\n\r\n Errors occur in H_LIB when trying to open currently open file.\r\n\r\n If, while working in a file in H_LIB, you select File Open and enter the\r\n name of the currently open file, errors will occur if you immediately save\r\n the current file or proceed to reread the current file.\r\n\r\n If you enter the name of the currently open file in the File Open box by\r\n mistake, do not accept the \"Save \" prompt if it comes up.\r\n Instead, escape back to the main menu and save your work.\r\n\r\n Blank help contexts may confuse H_CONVRT.\r\n\r\n If you are upgrading from a prior version of C-Worthy, and your help files\r\n contain help contexts with no attached help, H_CONVRT may convert the files\r\n incorrectly. If this occurs, simply use the HELPLIB that came with the old\r\n version of C-Worthy you have to attach a small amount text to each of the\r\n blank help contexts in your old help library. H_CONVRT will then convert\r\n the file correctly. You can then use H_LIB to make the contexts blank\r\n again, if you wish." }