Clicking on the Imagemap links will still take you to the zoomed-in note that you click on. But the topmost and map-containing page will now display its children compiled (or blocked) headings.

A subsection may now have its own Tables of Contents.

With more and more people using BoxPress for seminar TinderPoint presentations, we have decided to prioritize local file use. All media is now local-first.

Do not worry: When you paste your onto your webhost server, it grabs from the same directories as before.

… and better organized by theme.

A long-standing ^outboundBasicLinks^ bug will be fixed in the next release of Tinderbox. Currently, Tinderbox cannot calculate the correct urls for Basic Links to and from compiled child notes. The problem: the Tinderbox export code calculates the path relative to this rather than to current, ensuring that every path for compiled descendants is wrong.

Coding a system for adequate export has been so daunting that for 18 years no one had even tried to export a Basic Link with ^outboundBasicLinks^ from a compiled child note. BoxPress is proud to have initiated another Tinderbox improvement.

You can see the failure in action by going to the Granularity Explorer below. (Note that Basic Links work fine for the exported “envelope” note.)

Granularity Explorer

Bill Bulko suggested constructing the proper path by adding the full url of the destination (or source) note to the returned string and then using a replace regex to strip the quotes, graft the right sub-path into the url, and re-quote it. Something that would begin like this:

^basicLinks("<ul>","<li>^url(source)^","</li>","</ul>")^

I declined and emailed Mark Bernstein. This is something that should actually work for all exporters, and not just be a BoxPress feature.

Back in 2017, ^outboundBasicLinks^ returned an incorrect path in a different way—by adding surplus parent directories. But the fix there was a simple matter of snipping a number of directory levels equal to the this note’s outline depth:

^if($blogExpOpt.contains("INLINKS"))^
	^action( $tmpStr1(bstVAR)= ^inboundBasicLinks(,<li class=’li-inlink’>, </li>,)^ )^
^else^
	^action($tmpStr1(bstVAR)=;)^
^endIf^
^action( $tmpStr1(bstVAR)= $tmpStr1(bstVAR) + ^outboundBasicLinks(,<li class=’li-outlink’>, </li>,)^ )^
^action($tmpStr2(bstVAR)= ’$tmpStr1(bstVAR).replace("(\.\.\/){’ + eval($vCurSubDepth(bstVAR)-1) + ’}(\w)", "$2")’)^
^action($tmpStr3(bstVAR)=eval($tmpStr2(bstVAR)).replace("\\", ’’))^
^if($blogExpOpt.contains("INLINKS"))^
	^action( $MyString(bstVAR)= ^inboundBasicLinks(,<li class=’li-inlink’>, </li>,)^ )^
^else^
	^action($MyString(bstVAR)=;)^
^endIf^
^action($tmpStr1(bstVAR)= ^outboundBasicLinks(,<li class=’li-outlink’>, </li>,)^ )^
	^action($tmpStr2(bstVAR)= ’$tmpStr1(bstVAR).replace("(\.\.\/){’ + eval($vCurSubDepth(bstVAR)-1) + ’}(\w)", "$2")’)^
	^action($tmpStr2(bstVAR)=$MyString(bstVAR)+$tmpStr2(bstVAR))^
^action($tmpStr3(bstVAR)=eval($tmpStr2(bstVAR)).replace("\\", ’’))^

Line height in Map View in version 8.6.2 is 1.5. Since maps need to miniaturize to be readable, this has caused problems for Map View users.

No problem! Before you Copy View as Image, just set your line height in the Text Pane to Exactly and [66% of the font size]. For example, if your $TextFontSize is 12, set line height to Exactly and 9.

After you copy view to construct your Imagemap, just restore the original line height.