| Previous Next | Contents |
vml/svg.bitmap – updated to use the second part of a split filename as the content for the Xlink tag, as this is how the client should ask the server for the file. Clearly it is not likely to be the same as the local path to the file, and could even be a different filetype.
svg.bK – should draw a solid edge around a semi-transparent fill (was using the opacity setting for both fill and edge). Fixed.
Gradients – initial id set to 100000|Œai[2] (rather than 1) as we could assemble several charts into a single ‘slideshow’ where it is essential that the gradients all have globally unique ids.
Pie wedges – line-join set to ‘round’ to prevent narrow wedges making an ugly spike at the centre when the edge-weight is quite thick.
VML text – hibit characters now all output as &#nnn; style which dodges any issues with Unicode translation outbound from Dyalog-10 when called from C#. There is still a potential problem with these being passed in as Unicode strings, which Dyalog does not currently handle very well.
Bookmarks – bookmarks including ‘%’ characters fooled the parsing of the PostScript comment and crashed the PDF production. Fixed.
SVG titles – were not being given the &# treatment which upset the viewer for certain German characters like ü which is now ü and works fine.
vml.Log – was incorrectly generating id= attributes for markers and bars when the data series had the default name. Fixed.
Flowbox – adds support for hint/tip/href/jscript settings. Not all of these work on all environments yet (PDF does href only) but you can have jumps and tips in SVG and VML on (for example) the chart frame and XZones.
PDF Markers – some issues with character markers in the range above 128 (e.g the ‘heart’ symbol in ZapfDingbats) so these are now written out with the octal equivalent to keep the output as lo-ascii.
VML Markers – were slightly mis-positioned horizontally when hi-bit characters were used as markers. Fixed
JPEG support – JPEG images are now supported native in PDF documents. This keeps the document size reasonable if big images are included. All pictures are now included only once in the PDF however many times they are referred to in the original spool file. This allows the use of simple images like company logos at an acceptable cost in file size (particularly if JPEG is used).
PDF creation – will accept a list of spool files and create a single PDF from the entire set. This merges up the outline tree correctly, and will accept files in a mixture of paper sizes or orientations. Note that it is the responsibility of the generating application to number the pages sequentially.
Note also that bookmark resolution is not supported across multiple files, so you cannot use ‘Page &p of &n’ here (&n will resolve to the number of pages in each section) or build a consolidated TOC using bookmark references.
PDF,VML,SVG – all tolerate the ‘mirrored’ format required for HTML generation by removing all mirrored lines at the beginning.
SVG keys – adding effects to lines really should put the effect on the key. Due to an SVG viewer oddity, if a polyline has zero y-dimension (even though it is quite a thick line) adding a filter simply hides the line. Now we make a little undrawn T-piece at the end of the line in the key, and it works nicely.
SVG styles – the original SVG viewer required any CSS properties to be buried in a style=”font-size:nn; ... “ tag. This is ugly, and makes it really hard to modify selected attributes with JavaScript. The newer viewers are happy to take all these as first-class SVG attributes, so they are now recoded as font-size=”nn” in approved quoted style.
Event-handlers – extended to any ‘boilerplate’ elements such as keys, headings, axis labels and so on. Berserk example BscriptSVG tests everything I can think of at the moment. Note that if you specify the same handler several times, it is the last one that counts. This is relevent for chart notes where you could have different mouse-actions on different notes.
© Copyright Causeway Graphical Systems Ltd 1996-2004