Useful if current file has more than one map in it. You can then choose which map to open.
New maintainer of the MM/LX source code and responsible for future enhancements and bugfixes:Daniel Hertrich, Germany http://www.daniel-hertrich.de/contact
To each map a meta file is saved now (mapname.MM~), which holds information about the view setup. See below.New menu item Menu / View / Reset view which deletes that meta file and returns to the default view of the map (using Collapse=X in MM.CFG and centers the top item of the map).
New status in top line in front of the file name:
"**": File contents are modified (as before)
"*": Display setup modified (meta file can be saved) (NEW)
Following actions cause a change in the internal meta info
and the "*" to appear in the top line:
- moving the cursor to another item
- Panning the map with Shift-Cursor key
- Zooming the map (Fn-Space)
- Hiding / unhiding a subtree (Alt-H)
- Modifying the "Branches to the right" setting (Alt-R)
- L/R/Center map (Alt-Z)
- Collapse at (Alt-C)
- Viewing a submap (Alt-T)
- Returning from submap view (HOME)To save the meta info to the MM~ file, press F10.
If "*" is displayed, but not "**", MM/LX does NOT ask on quit or close of the map if the meta file should be saved. This is to avoid annoying questions if a map has only been browsed and not modified. If the view setup should be saved but the map contents have not changed, F10 MUST be pressed explicitly to save the view setup.
Since the "branches to the right" setting is saved in the meta file, NumRight setting in MM.CFG is meaningless now and can be deleted.
Multimaps are handled the following way:
* If multi map is saved, meta file saves display state only for
displayed map.
* If multi map is opened without a link to a map (#MAPNAME) and a meta
file for the map file exists, MM/LX jumps directly to the map which
the meta file was saved for.
* If multi map is opened with a link (e.g. help.mm#HELP), meta file is
disregarded but not deleted.
* Multi Map menu is only shown if no link is given and no meta file exists.
* If Multimap is re-opened with Ctrl-F9, meta file is deleted in
background, so that on re-open, the menu with map parts is displayed again.Hint: If the map file has been changed outside MM/LX (e.g. in PE), the MM~ file should be deleted to avoid problems with display setup (e.g. if an item has been deleted from mm file, but meta file wants to highlight that item, we get serious problems!) MM/LX tries to detect if the MM~ file fits the MM file, but this test may fail. If MM~ file is detected to be invalid for the opened map, the map is closed again and the MM~ file is deleted. Then the map can be reopened without loading the view setup from the MM~ file.
A format description of MM/LX meta files is supplied with METAFILE.DOC.
New search feature: Using Crtl-S you can search for a string in the entire map (including links and notes). The search is case insensitive, i.e. "hello" will find Hello, HELLO, HeLlO and so on.With Alt-S, you can continue the current search ("Find next").
The search is always only performed in the displayed (sub)map. It you want to search in a multimap, open the map file in an editor and use the editor's search feature.
For search, there are two new menu items in the Edit menu.
is more intuitive now. On quit, MM doesn't save the map without asking before. It is also possible to discard the changes. Questions "Really....?" default to "NO" now, which is safer that if YES is the default.
On "Reopen map" (Ctrl-F9), MM now asks if map should be saved before reloading (if modified), or if old version should be loaded.The Meta file is deleted, so that on the re-opening, the menu is shown where the user can select the map section to open. View setup data is lost of course.
to avoid annoying questions, it may be convenient to put clog=0 into the [System] section of MM.CFG
New status indicator in top line, in front of the file name:
"**": File contents are modified (as before)
"*": Display setup modified (meta file can be saved) (NEW)
New indicator in top line "MULTI", if file is a multi map file.
New indicator in top line "SUB", if only a submap is displayed.
(don't confuse submaps and multi-maps!)The indicators SUB and MULTI are blinking by default. If this is not wanted, it can be switched off with the entry FlagBlink=0 in the [System] section of MM.CFG.
Highly improved HTML export:Formatting of notes is now preserved: Newlines in a note are converted to 'BR' HTML tag. So lists or enumerations etc. are more readable in the HTML.
If a Multimap is exported, user can choose if entire multimap or only currently displayed map is exported.
Multimap export generates an index at the top of the HTML page (can be deactivated using HTMLIndex=0 in [System] section of CFG). The links include the map date, if there is any (in v2.0, the date was never exported into the HTML). This is especially useful for generating meeting reports from meeting note maps. Between each section there is a horizontal line and a "back to top" link.
Syntax of HTML file is now compatible with more browsers (HTML code caused problems with Opera and Konqueror, for example).
Font sizes for items and notes are now seperately configurable with HTMLSize= and HTMLNSize= in [Fonts] section of MM.CFG. Defaults (if not given in CFG) are HTMLSize=+1 and HTMLNSize=+0 For examples see supplied MM.CFG.
F6 = ALT-H = Hide/Unhide subtree. If you had any macro defined on key F6 (0x4000), you'll have to delete it or redefine it for another key, e.g. Shift-F6 (0x5900).
Simple scrolling is now possible in the built-in notes viewer. If screen is full, press a key and next screen is displayed. If last screen is displayed, press any key to return to map. Press ESC or F9 in any note screen to return to map view.However, to achieve more convenience with displaying notes, it is recommended to use an external viewer, such as Vernon Buerg's "list" (www.buerg.com). See MM.CFG section how to use an external viewer for notes.
If on the command line a file name without extension is given, MM/LX now automaticlaly appends .MM as the extension.
When editing the top item of a map with date (meeting notes...), the item description dialog did not show the date and it could not be edited. Now the date can be edited and if the date is not removed (but kept or modified), it is placed in the top line again after the next saving.
If several maps are open and you changed the zoom mode of one and closed it thereafter, zoom mode was used also for next map, but positions of items weren't recalculated.
New file name given at "save as" prompt was used for saving, but not shown in message dialog "Saving ...". There the old file name was displayed.
After loading a template into a new map, saving failed and data of map was eventually lost. This should not happen anymore now.
"hide Subtree" (Alt-H) was possible even when there were no children of marked item ("+" was displayed, although no children were hidden).
If a child was created of an item with a hidden subtree, it caused problems. Now the subtree is first expanded automatically, then the child is created.
If a section name of a multi map contained a link to a file or map (Ctrl-F / Ctrl-M). and if the map was opened with a link, which did not contain the file/map link, but only the section name (e.g. when beeing in that section and pressing F10 to save the map), loading failed, because section could not be found.
If items with notes changed their level (e.g. with copy/paste or with delete/promote or insert/demote), the note indentation was not changed. This resulted in working but formally wrong MM files. This behaviour is changed now, as when saving a map, each found note indentation is removed and replaced by a new indentation according the the item level.
HTMLs generated with the HTML export feature now look nicer than before. Browsers supporting CSS (cascading style sheets) interpret the new HTML header data which applies font and color formatting and some graphical elements such as borders, lines etc. to HTML objects.Either MM/LX's built-in style sheet can be used or an external one. The built-in one can be customized via MM.CFG.
Usage: On exporting with CTRL-P, you are asked which style to use. There are two cases to be distinguished:
CASE 1: Enter 0 for "no or external style sheet". A link in the HTML will be generated which points to a style sheet file "mystyle.css". If that file exists in the same directory where the generated HTM file resides, it is used by the browser and applied to the HTM file. If mystyle.css does not exist, the browser disregards the link and thus no style sheet is used at all.
CASE 2: When entering a number >0, the built-in style sheet is used, together with the settings in MM.CFG from section [HTMLx] (x being the number you entered). E.g. enter 2 to use the built-in style sheet with design settings from [HTML2]. This way the user can choose between multiple designs, logos etc. without editing the MM.CFG file each time another design has to be used.
The user can define up to 9 different designs [HTML1] .. [HTML9]. A design includes a company logo (optional), all font / border / background colors, logo position, border width, padding etc.
There is a new command line switch of MM.EXE /sX or -sX, X being the design to use (= the number you enter in the style design dialog). So, to export map example.mm with an external style sheet, use MM.EXE -h -s0 example.mm. To export with the internal style sheet and design 1, use MM.EXE -h -s1 example.mm.
Read HELP.MM to learn details about the various HTML design settings.
All entries in [System] and [Fonts] beginning with HTML... are not used anymore. Instead there are new sections [HTML] and [HTMLx] which hold these old entries (with new names!) and a lot of new entries. See HELP.mm#MM.CFG for more info.To restructure your CFG file, do the following: * Keep the [System] / [Fonts] HTML... entries for reference * Copy the [HTML] section from the supplied example MM.CFG file to your own file (at the end is okay) * Copy the [HTML1] and [HTML2] sections from the supplied MM.CFG file to the current MM.CFG file. * Apply your old values to the new entries. The entries are renamed:
Old entry New entry in [HTML] ===============================
HTMLFooter: Footer HTMLIndex: MultimapIndex
Old entry New entry in [HTML[1|2]] ==================================== HTMLSize: FontSizeItems HTMLNSize: FontSizeNotes HTMLFont: FontFamily (attention! other valid values than before!)
* Delete the old HTML... entries in [System] * Restart MM/LX
Read the comments for all the new MM.CFG entries in HELP.MM#MM.CFG!
If a map is exported as HTML and the map has more than 4 levels (including the root item), a warning is shown that HV (HTML viewer by Andreas Garzotto) will not display the HTML correctly. HV only supports up to 4 levels of nested lists. The warning can be deactivated by HVLevelWarn=0 in [HTML] section of MM.CFG
In the file open dialog you can press TAB to expand the file name. "MM~"-files (MM/LX's meta files) are skipped now in this procedure, because they cannot be loadable maps anyway.
When uploading HTM files containing links to a webserver with a case-sensitive file system, such as UNIX or Linux servers, links in the HTML may not work depending on the way the user transfers the files from the palmtop to the server. LinksUpperCase controls the letter case for file links. Default is 0 (lower-case), 1 is upper-case. So if the HTM files generated by MM/LX are turned upper-case when uploading to the webserver, use LinksUpperCase=1 and regenerate the HTM files.
When taking meeting notes, usually one branch of the map is called "Todos". Now it is possible to export these items as Todos into a PIM/PE file. Mark such an item and press Alt-D. A calendar is shown where the "due date" (date until which the todo has to be done) can be chosen. As the start date, the current date is used. Press ESC to export the Todo withouth a due date. Cursors move through days/weeks, PgDn/PgUp move through months. Enter selects date. If you use priorities in PIM/PE, append them to the map item as you would append them in PIM to the +t line. They are exported with the Todo item. After successful export, the map item is marked as done, so the user knows it has already been exported.Related Menu items: Menu "Extra" "Export Todo" (=ALT-D).
Related new MM.CFG entries: Section [Extra]: TodoExportTo=: PIM file name TodoExportDone=: choose if exported items should be marked as "done" in the map. IsoDate=: Adjust that to the IsoDate setting in PIM.CFG. If 0 (default), dates are generated as DD-MMM-YYYY (16-JUN-2004) If 1, dates are generated as YYYY-MM-DD (2004-06-16) PimRebuild=: Set command to rebuild PIM indexes If anything has been exported to PIM/PE from a mindmap, on saving or closing the map the user is asked if PIM indexes should be rebuilt (recommended!). PimRebuild sets the command line to do so ("pim -r" is the default).
Also take care about the setting [HTML] / StripPIMPrio. By default, if you export a map as HTML, the entire item text is exported. If you use PIM ToDo export, you may use priorities in the todo texts. It may be desirable to strip them when exporting as HTML. Set [HTML] / StripPIMPrio=1 to strip priority info when exporting. Attention: Do not use '#' in item texts except for priority info then!
Now on exit, if view setup has been modified, metafile is saved automatically. This behaviour can be switched off with SaveMetaOnQuit=0 in [System] section of MM.CFG. If switched off, F10 must be pressed to save the view setup (same behaviour as in version 3.0).
Just created children or siblings sometimes were outside the screen area and not paned into the screen area automatically.
Every img tag in the HTML export of a map caused the image to be placed in the upper right corner of the HTML, because MM/LX uses the img tag also for the company logo and the style sheet did not distinguish between a logo and a regular image. Now it distinguishes between both img variants by using the class "logo" for the logo image.
When exporting a Todo, the newline bytes before "Todo from Mindmap XY" were wrong (only an LF, no CR). Now it is written correctly as CRLF. Recommended: Correct the todos exported so far with the command gsar -s:010Todo -r:013:010Todo -o PIMFILE.PIM (you need the gsar utility for this).
Usually on cutting / deleting an item, the cursor moves to the item which is stored previously to the deleted one in the MM file. If that item was hidden, the cursor was not displayed and it was sometimes difficult to get it back (using the cursor keys). Strange mark / unmark things happened on the screen. Now, if the previous item in the file is hidden, the cursor moves to the first visible parent of that item.
If a map has been modified, then closed without saving, the metafile WAS saved, so it didn't fit the MM file anymore. This resulted in an "invalid metafile" message on reopening the map. Now in such cases the metafile is not saved as well.
On Delete/Promote item (Ctrl-Del), the entire map display was recalculated using the Collapse= value in the CFG file, discarding the current view setup entirely. Now the view setup is preserved.
On HTML export, ESC now really escapes on every menu / dialog. On PIM Todo export, notes were written with MM/LX's indentation character and spaces in front if each note line.
There is a new section [Designs] in MM.CFG. There, Aliases for the design numbers are given. So if you have [HTML1] for the report design of company XY and [HTML2] for design of your personal website, the section [Designs] would look that way:[Designs] &XY=1 &Private homepage=2
If you use several different designs, and if you haven't specified "UseDeisgn" (which overrides all manual settings), you will NEED that new section. As always in menues, you can give the & character in front of the character you want to make the hotkey for the entry.
Images can be embedded in a HTML export now by using the file link feature (Ctrl-F). Create an item, press CRTL-F to link it to a file. As the file name, enter any file or URL with the file extension .jpg, .jpeg or .gif.If the map is exported as an HTML, the IMG SRC tag is used to create a page with inline images.
This behaviour can be switched off by using EmbedImages=0 in MM.CFG / [HTML]
Or: Menu / Extra / Extract Submap:If your map gets larger and larger, you may want to swap parts of it out into another file. Mark the item which leads the submap you want to extract and hit Alt-X. You are asked for a filename (a name fitting the item text is suggested, you may modify it). Press enter. A new map is generated with the marked item and its children. In the original map, the marked item in the original map is converted into a link to the new map.
Note: If the item contained a note, this is also migrated to the new map and deleted from the old one. If the item was a link before, the link is lost and replaced by the link to the new map.
To open the new map, you may simply hit enter on the marked (and now underlined) item.
If a done item at level 1 was exported, MM created an "I" opening tag instead of an "EM" opening tag. The following "/EM" closing tag did not undo the "I" and thus all the following was displayed in italics.
In very special cases when Alt-X (Extract submap to file and create link) was used, it resulted in data loss. The critical situation was: If you used Alt-X on an item wthout children which was followed (in the MM file) by an item with lower level. In such cases all items with _lower_ level _until_ the next item with the same level as the Alt-Xed one would be lost.
If a file should be opened which resided in the root directory of a drive, and if the file name is given as c:\name.mm or \name.mm, MM did not open the file but suggested creating a new file. This was a bug in processing the given file name.
Under certain circumstances, the export engine generated two level 1 headings (H1 tag) at the top of the HTML file, instead of just one. This should be fixed now.
A collapsed branch of level X+n remains collapsed if a branch of level X is collapsed and expanded again.Until this change, if a branch was expanded, ALL subbranches were expanded, too, no matter if they were collapsed before or not.
The information if a branch is shown or collapsed is saved in the metafile (*.MM~).
In each HTMLx design section the Dir= parameter sets the default directory into which to export the HTML file. No backslash at the end! This can also be set in [HTML] to be valid for all designs. If set in [HTML] and [HTMLx], the value in [HTMLx] overrides the value in [HTML] if design x is used.
If you give a file name here, no design data is taken from the CFG file but a link to the given CSS file is inserted into the HTML file instead. Like the "external design" feature (design 0), but with configurable file name. This can also be set in [HTML] to be valid for all designs. If set in [HTML] and [HTMLx], the value in [HTMLx] overrides the value in [HTML] if design x is used.
By default, backslashes in map file links are converted to slashes (if a map link was "..\mydir\mymap.mm" and the map containing that link is exported, the link in the HTML file is written as link title To preserve the backslashes, use LinkSlash=0 in [HTMLx] or, for global setting, in [HTML]. The [HTMLx] setting overrides the [HTML] setting if design x is used.
If given, the given string is appended to the bottom of the HTML page.
HTMExt may be used in a HTMLx section or globally in the HTML section of MM.CFG. It sets the file name extension for the created HTML files.
Font size of headings can be given here. Defaults are relative font sizes: 110% for H3, 120% for H2, 140% for H1.Can be given in any CSS-compliant font size unit, e.g. 150%, 16px, 3mm....
When setting config parameters, many parameters can now be given in [HTML] as well as in [HTMLx] sections.If set in [HTML] this is the global setting for all designs. If set in [HTMLx] it is only applied to design x. The [HTMLx] entry has a higher priority. I.e. if you export a map with design x, MM/LX first looks for the parameter in [HTMLx], then in [HTML] and if not found, it takes the default value.
This method is applied to the following CFG entries:
CSSFile Dir LinkSlash MultiMapIndex MultiMapLines EmbedImages Logo StripPimPrio FollowLinks LinksUpperCase HVLevelWarn Footer MyFooter
Switch this feature on with [HTMLx] / FollowLinks=1. Can also be set as [HTML] / FollowLinks=1. The setting in the used [HTMLx] overrides the [HTML] setting.What it does: Each map link (Ctrl-M) which is met during HTML export of a map is remembered. After the export of the original map is finished, all remembered maps are also exported (without asking for file names. PATH\NAME.MM is converted to PATH\NAME.HTM). Each map link in such a remembered map is also remembered etc. This way it is possible to convert an entire MM/LX "web" to HTML. useful for webites created by MM/LX, for example. Just convert index.mm and MM will convert all linked files. This also works for files in subdirectories. If no Dir=... is given in the corresponding [HTMLx] section of MM.CFG, the HTMs are placed where the MMs are stored. If Dir=c:\example\path is given, the directory structure of the MM file site must be existent under c:\example\path too. The HTMs are then placed in the corresponding subdirectories of c:\example\path.
If embedded images are used in HTML export, the "item" is now shown with the image file name on top.
For an internet link (useful when creating websites with MM/LX), add an item for the link with a description as the item text. Then press CTRL-F (File Link) and enter the complete URL with leading "http://". On HTML export, this link will be kept as is (no letter case conversions etc. as applied to normal file links)
For each item an A NAME tag is generated no, containing the item text as the name (spaces converted to underscore, all letter cases converted to lowercase).So the item "Dinner for one" gets a name tag [A NAME="dinner_for_one"]
This makes it possible to link to an item from another item or from a note etc.
New default: Note sections with only line breaks but without empty lines are exported as floating text. An empty line in a note causes a [P] tag to be generated in the HTML (new paragraph).This behaviour can be modified by using the NoteFormatOnTag within the note. This may be desireable if the note contains consecutive lines with formatted text, e.g. lists, enumerations etc.
To switch back to default formatting behaviour, use the NoteFormatOffTag.
The defaults (if not given otherwise in MM.CFG / [HTML]) are (see this note as an example):
NoteFormatOnTag: NF1 (in HTML tag braces)
NoteFormatOffTag: NF0 (in HTML tag braces)
NoteFormatOnTag (default is NF1 in HTML tag braces) sets the tag which can be used to tell MM/LX to preserve formatting in notes. NoteFormatOffTag (default is NF0 in HTML tag braces) sets the tag which can be used to switch that formatting preservation off.Preserving formatting means that MM/LX inserts a BR tag for each new line of a note. This is useful for lists, enumerations etc. However, it is desirable for floating text ont to be formatted this way.
If no tag is used in a note, the default is that the formatting is NOT preserved.
This parameter cannot be given in [HTMLx] sections; it is HTML-global only.
Path handling modified. Always works internally with full path names now (necessary for correct handling / following of relative map links).Relative paths in map links should be handled correctly now, also when exporting an entire website with links to maps in subdirectories etc.
This is transparent to the user, the user should not see any change, except that the top line now always shows the entire path of the currently loaded map. If that path is too long for the top line, it is shortened by cutting a piece from the middle and replacing it with "...". E.g. in the top line would be displayed
a:\this\is\th...the\mindmap.mm
instead of
a:\this\is\the\path\to\the\mindmap.mm
Since 3 spaces at the beginning of a line in the raw MM file mean to MM the line is an item with a certain level, leading spaces in a line of a note can disturb MM when loading the file, resulting in file corruption. Now if a note is entered, and if a line of the note contains a space as the first character, this space is converted to a dot (.) This preserves the note formatting, at least when viewed in MM/LX, but avoids the problems with leading spaces. Example: The following line . has been entered with 6 leading spaces. . This line had 9 leading spaces. (the dots above were not entered by the author, but MM/LX added them automatically).Note: This new feature is only relevant for saving the map. on loading, the dot is treated as every other normal character and not interpreted in any way.
For a list of files for PIM Todo export. On Alt-D, MM/LX shows a list of PIM files to choose from.If only one PIM file shall be used, use the [Extra] / TodoExportTo= parameter which gives the name of the PIM file to export to.
If you want to choose from several PIM files, delete the entry TodoExportTo= and instead use this [PIMFiles] section. Each line in this section gives one file name.
Format of a line: FileDescription=c:\path\filename.pim ("FileDescription" is the string which is displayed in the menu). An ampersand character in front of a letter makes that letter the hotkey.
There was a bug in the HTML link generation in converting non-alphanumeric characters to underscores which prevented some links from working properly.
When a multimap was exported and the map index was generated at the top of the HTML page, conversion of non-US-ASCII characters was done in a wrong way in the index.
After selecting an item using a hotkey, the map was not panned to that item, resulting in the marked item to be invisible if it was out of scope before pressing the hotkey.
If the path and file name of a map plus the name of a multimap was too long (more than abt. 80 characters all together), the map reload after saving the map, or loading the map via map name link, failed due to a too small character array in the code. Symptoms: Either the message "New Map - Empty map, use template, cancel", or a total crash of MM.EXE. The saving was done successfully, so even when MM.EXE crashed there was no data loss.
When pressing ESC in calendar, generation of new map can be avoided. Otherwise the choosen date ist used for the new map. So the new map's date is not limited to be "today's" date.
After deleting the marked item (DEL), another item has to be marked. The choice of the item to be marked is more sophisticated now.The mark does now not go outside the current subtree anymore and does not go into a higher level.
That is, on deleting an item, the mark goes to the previous or next sibling. If there is no direct sibling, the mark goes to the parent of the deleted item.
If the Enter key has nothing else to do (following link, viewing note), and if "ENTEREdits=0" is given in MM.CFG [System] (means that enter does not edit the item name) and if marked item is a collapsed subtree, Enter expands that subtree instead of doing nothing.
With version 2.3 of the PIM application reindexing after Todo export from MM/LX is not necessary anymore. So the question "Reindex PIM?" when a map is saved from which todos have been exported is removed. Parameter MM.CFG / [Extra] / PimRebuild is obsolete and can be deleted.
The search feature (initiate search with Ctrl-S, continue search with Alt-S) now searches more than the currently displayed map.If a submap is displayed, after searching the submap the entire map is searched.
If current file is a multimap file, after searching the currently displayed map (and maybe the entire map, if a submap was displayed), all the maps of the multimap file are scanned for the search string.
Created with MindMap/LX