MswLogo Version 3.4c for Micro-Soft Windows 3.0,1 is ready !!! ------------------------------------------------------------- Contents -------- Part I) Kit Description/Location: Part II) New features/bugs fixed: Part III) Installation: Part IV) Standard features: Part V) Recommended usage: Part VI) Bugs / Missing features / Wish List: Part VII) Reporting bugs: Part VIII) Sources: Part IX) Minimum System Requirements: Part X) Public domain Logo's (on IBMPCs): Part I) Kit Description/Location: The "base kit" is for users with Windows 3.1. The "extensions kit" is for Windows 3.0 users. The "extensions kit" is not a FULL kit, you still need the "base kit" for any installation. The "base kit" includes the only documentation in Microsoft Windows Write (.WRI) format. You can load it into Write and print for any format you have drivers for, including postscript. mswlgo34.zip (base kit: Windows 3.1) mswext34.zip (extensions kit: Windows 3.0) mswsrc34.zip (source kit: @ char.media.mit.edu only) You will find kits at the following locations. itrc::/millspub/mswlgo34.zip (this is a DEC internal location) (vms:$ spool copy itrc::"/millspub/mswlgo34.zip" []mswlgo34.zip) or cher.media.mit.edu on pub/comp.lang.logo/programs/mswlogo or simtel on PD1: (in queue) or Send the following message to: ftpmail@decwrl.dec.com ----cut here---- connect 18.85.0.47 binary uuencode chdir pub/comp.lang.logo/programs/mswlogo get mswlgo34.zip quit ----cut here---- Send the following message to: ftpmail@decwrl.dec.com for more information on ftpmail ----cut here---- help ----cut here---- Note: The ftpmail server suggested here it is a common service to internet users from Digital Equipment Corporation. You can also obtain an installation floppy by Postal Mail. Send a Self-Addressed (Post Paid) package to: George Mills 33 Thoreau Road Northboro MA 01532 The package MUST contain a 1.44 or 1.2 Formatted Floppy. Since the kit is getting large and expensive to down load I don't mind anyone asking for it by Postal Mail. Part II) New features/bugs fixed: o 3.4c -- Turns out most of the problems on the 3.4 release were due to user's system problems. Due to a change I made in looking for a problem in 3.4, 3.4a gets STACK OVERFLOW on some commands (mainly to and readlist) commands. This is fixed. While hunting for causes of non-existent problems I found ways of reducing the resources that MswLogo requires (which is in this release). o 3.4c -- A change due to go into 3.5 slipped into this release. The listboxgetselect now returns a list instead of a word. o 3.4c -- Another change due to go into 3.5 slipped into this release. The screen background color was not using the palette. o 3.4c -- Another change due to go into 3.5 slipped into this release. The calc.win example is now in sync with the API once again. o 3.4c -- One problem that caused some grief is that some systems have a bad copy of VER.DLL. The one that comes with Windows 3.1 should be located in \WINDOWS\SYSTEM. The bad copy is usually in \WINDOWS. A good one looks has 9008 bytes and date of 08-26-92 3:10a. This may vary though. I believe some application(s) install the bad one. The bad one causes logo to install incorrectly. If no copy of VER.DLL exists the SETUP program supplies its own copy (This happens on Windows 3.0). o 3.4c -- A problem some systems had was improperly set TEMP environment variable. TEMP should be defined as something like SET TEMP=C:\TEMP and C:\TEMP directory must exist. If a space exists on the left of the "=" then you have not defined TEMP but defined "TEMP " and will not be see by any DOS or Windows application. If a space exists to the right of the "=" then Windows INVALIDATES the definition and no windows application will see it. The first character after "=" must be a valid drive letter. Try finding that in a book !!! o 3.4b -- A couple select users received this version for debug only. o 3.4a -- Fixed MswLogo to handle TEMP not being defined correctly. o 3.4a -- Fixed bug in which wait command did not YIELD. This caused the echo.mci example to not run. o New INSTALLATION program!!! The install method is a true blue Windows installation program. I have found a lot of friends that are interested in MswLogo but say "What's a ZIP" and end up helping them. Most folks that are internet/compuserv literate have no problem with the old method. The kit, is of course still zipped. But now you can make a simple "installation" floppy from the kit. So make a Floppy for a friend or your School !!! o Fonts have been incorrectly done in the past. They are now done correctly and also have a Graphical user interface to set them. The graphical user interface is only available on Windows 3.1. See set Menu. Note also that the font commands have been restructured (much easier and full control). o There is now graphical user interface for setting colors. See Set menu. o You can now Test (execute) multiple lines of code from the editor. Just select the code with the mouse and click on Test in the Editors Menu. o SCROLLBARCREATE is yet again fixed. V3.1 Broken, V3.2 Fixed, V3.3 Broken and V3.4 Fixed. I did not like the fix in V3.2 so I tried to fix it again in V3.3 and failed. V3.4 has the same fix as in V3.2. o Lots of Memory Leaks (using memory and not giving it back) are fixed. o Halting while in a .macro sometimes caused a crash. This is now fixed. o Editor could not handle more than 18K or less (shared between all instances of the editors). It can now handle 32K for each Edit instance. Even 32K does not sound like much but you do not have to edit everything within one instance of the editor at once. (Not fixed in Windows 3.0 version) o Editor could not handle lines longer than 1024 bytes. It now has no limit. 1024 sounds like a lot, but it's not. Since "Lists" can be edited and possibly generated by execution. In otherwords if you ran code that generated a list that was more than 1024 bytes, (very easy to do) then did an EDALL, you would not be able to exit the editor (reload would fail). Because the "list" would be broken ('s inserted without continuation). This may expalain some mysterious "Cannot RELOAD's" error messages that you could not determine the cause of. o File-New was a bit dangerous in that it would not warn you that your existing modified code would be erased with out giving you a chance to save it. It now gives you a chance :-). o File-Erase function was added to Menu for consistency/completeness. o Another awkward thing about editing was that when you deleted a procedure (or perhaps renamed it) it did not go away. It went away from the edit session but logo itself still retained it. This is because the exit of an edit caused a load to happen. Nothing was "erased". Now upon successful exit (no errors on reload) the old routines (only the ones you edited) are erased before reload. So remember that DELETING code in the Editor is COMMANDING logo to erase those routines when exiting the editor. So keep this in mind if you decide to use multiple Edit sessions of the SAME code. I believe "auto-erase" is much more intuitive (if you delete code it's really gone now!!). o A Dialog Editor (a visual editor) is supplied. It's a Logo program!!! A dialog editor is a fairly complex "Windows" application. "Visual" is a generous term in some respects. But I found it very usefull. You must understand it's limits and the LOGO-WindowsAPI routines to use it. The Dialog Editor was Written with the Dialog Editor :-) Developing the Dialog Editor also surfaced most of the problems with the Editor. o Added function to detect color of pixel under turtle. See PIXEL. o MswLogo 3.3 was missing the MultiMedia (MCI) Help file. I hope it's there this time :-). o The March 10, 1993 version of BWCC.DLL is supplied with this version of Logo. o Comparing (<,>) large integers would give incorrect results. This is now fixed. o You now have the capability of calling Windows Help with your OWN Help file. This allows you to provide Windows HyperText help for your own applications. To write Windows HyperText help files (.HLP) You need a Help Compiler. MicroSoft has put their Help Development Kit in the Public Domain. It is available on compuserv and internet. See "winhelp" for details of calling Windows Help. The Help Compiler Assumes you have access to a Rich Text Format (RTF) compatible Word Processor. MicroSoft Word for Windows is the most popular tool for this. o Some old UCBLOGO functions that did not work in MswLogo now do. (dribble works). o The HELP file had another MAJOR cleanup. It now includes a simple Example for EVERY function and includes the output the example should generate. o MswLogo did not process from the input control box like UCBLOGO does. To remove this problem I've added the control character "\n". So "\n" will produce a while interactive or from procedures. The \ (the UCBLOGO way) will also continue to work within procedures but will not work interactively. o All color functions are set and output as a [Red Green Blue] vector. They used to be returned as a vector and set as 3 arguments which was inconsistent. Now everything is consistent. Here are examples of the changes you might have to make in existing code: Before: setpencolor getred getgreen getblue Now: setpencolor (list getred getgreen getblue) Or a shorthand version if all your args are constant: Before: setpencolor 50 100 150 Now: setpemcolor [50 100 150] o The scratch file (temp file) that the editor uses is now placed where the standard environment variable TEMP points. Rather than the location of LOGO.EXE. This allows MswLogo to be installed on read-only mounted disks (Networks) while keeping the temp file local. o Commands time, getfocus and mci all return lists now rather than a raw string. o MCI command will finally to callbacks (notify is supported). So you can now CHAIN events together. o MswLogo has all the fixes included in UCBLOGO 3.0 Thanks to many folks for spotting many of these bugs. Part III) Installation: 1) Build a kit area on floppy or hard disk: C:\> format a: /u or C:\> mkdir logokit C:\> a: C:\> logokit 2) Unzip the kit to that area: C:\> pkunzip -d c:\mswlgo34.zip (You must use -d switch) 2b) For windows 3.0 (ONLY) you need to "modify" the kit: C:\> pkunzip -o c:\mswext34.zip (-o is for Overwrite) 3) Install it: C:\> win a:\setup or C:\> win c:\logokit\setup If you wish to add switches you still must do this manually, by changing the Icons properties (See Program manager File menu). Use switches "-h number" (to select height) and "-w number" (to select width). The default is 1000x1000. For example to change to a 500x500 image (using 1/4 the amount of memory) enter: c:\logo\logo -h 500 -w 500 Start it from Windows by double clicking the Logo Icon Start it from DOS by typing "win logo [options]" at DOS prompt (assuming logo.exe is in your PATH). Try typing "DEMO" in the "Input Box" (bottom most box in commander). Note if DEMO does not run you did not install it correctly. Part IV) Standard features: o Supports Text in all available fonts and sizes. o Cut, Paste and stretching bitmaps. o Zoom. o Tail recursion. o User error handling. o "Standard" Logo parsing. o Floodfill. o Save and restore images in .BMP format. o 16.7 million pen and background colors (using windows dithering). o Supports color palette (256 solid colors). o Standard Windows Hypertext Help. o Standard Windows Printing. o Supports separate library and work area. o Allows you to do real Windows programming. Part V) Recommended usage: o All ages, from beginner (Forward 100, Right 90) to expert (develop professional looking Windows Graphical User Interfaces). Part VI) Bugs / Missing features / Wish List: o Real mode is not supported. o SETCURSOR function is not supported. o Sound generation (Note there is a lot that CAN be done with MCI). o Multi-line Clipboard support. o Multiple Turtles. o DDE support o DLL support o Functions to add menu's Part VII) Reporting bugs: Report bugs to George Mills: internet: mills@athena.tay.dec.com compuserv: 71222,452 You can also report bugs to Brian Harvey: internet: bh@anarres.cs.berkeley.edu Part VIII) Sources: Sources are available at the kit area on internet only. If enough compuserv requests are made for sources I will make them available there as well. If you are working with ANY derivative of the UCB Logo sources Send me mail to be added to a mailing list so that we can all stay in touch. The Msw-Logo sources are written using: Borland C++ for windows (for .EXE) MicroSoft Word (for online help and DOCs) Dr. Help shareware (for online help and DOCs) Sources for Unix, DOS, and Mac are available from Brian Harvey by anonymous ftp at anarres.cs.berkeley.edu. Part IX) Minimum System Requirements: 286 with Minimum of 2meg running Window 3.0 in Standard Mode. Part X) Public domain Logo's (on IBMPCs): LADYBUG - Simple cute (barely logo) program. The thing that is impressive is how the author added music (using the PC speaker). CGA-DOS. NO support. UCBLOGO - Brian Harvey at Berkeley started over with this project and is a very good core. But again under DOS has a no graphical user interface. Supported. Best public Domain for DOS. Also available for MAC and UNIX (anonymous ftp from anarres.cs.berkeley.edu). MSWLOGO34 Graphical User Interface and UCBLOGO core. Supported. Best public Domain for Windows (that I know of at this time).