Skip to content
Commits on Source (5)
October 9, 2019
- Release 2.42.3
- Merge 1316, 1317, 1319, 1320
- Patches #1591, #1596
- Add Fedora 32 builds
- CI/CD fixes
- Documentation (Warning about HTML label usage)
September 17, 2019
- Release 2.42.2 - ( Never fully released due to CI/CD hardware issues )
- Fix deployment issues. Builds can now be found under:
http://www2.graphviz.org/Packages/
July 17, 2019
- Release 2.42.1
- Fix deployment issues. Builds can now be found under:
......
version: 2.43.{build}
#version: 2.42.1
#version: 2.43.{build}
version: 2.42.3
clone_depth: 25
image: Visual Studio 2015
......
......@@ -33,16 +33,16 @@ dnl For the micro number: 0 => in-progress development
dnl timestamp => tar-file snapshot or release
dnl uncomment the next 4 lines for development releases, minor version must be odd
m4_define([graphviz_version_major],[2])
m4_define([graphviz_version_minor],[43])
m4_define([graphviz_version_micro],[$GRAPHVIZ_VERSION_DATE])
m4_define([graphviz_collection],[development])
dnl m4_define([graphviz_version_major],[2])
dnl m4_define([graphviz_version_minor],[43])
dnl m4_define([graphviz_version_micro],[$GRAPHVIZ_VERSION_DATE])
dnl m4_define([graphviz_collection],[development])
dnl uncomment the next 4 lines for stable releases, minor version must be even
dnl m4_define([graphviz_version_major],[2])
dnl m4_define([graphviz_version_minor],[42])
dnl m4_define([graphviz_version_micro],[1])
dnl m4_define([graphviz_collection],[stable])
m4_define([graphviz_version_major],[2])
m4_define([graphviz_version_minor],[42])
m4_define([graphviz_version_micro],[3])
m4_define([graphviz_collection],[stable])
m4_define([graphviz_version_date],[$GRAPHVIZ_VERSION_DATE])
m4_define([graphviz_change_date],["$GRAPHVIZ_CHANGE_DATE"])
......
......@@ -499,7 +499,7 @@ In particular, if a node has set its
attribute to <TT>none</TT> or <TT>plaintext</TT>, the HTML label will be the node's
shape. On the other hand, if the node has any other shape (except
<TT>point</TT>), the HTML label will be embedded within the node the
same way an ordinary label would be.
same way an ordinary label would be. Adding HTML labels to record-based shapes (record and Mrecord) is discouraged and may lead to unexpected behavior because of their conflicting label schemas and overlapping functionality.
<P>
The following is an abstract grammar for HTML labels.
Terminals, corresponding to elements, are shown in bold font,
......
......@@ -54,7 +54,7 @@ In particular, if a node has set its
attribute to <TT>none</TT> or <TT>plaintext</TT>, the HTML label will be the node's
shape. On the other hand, if the node has any other shape (except
<TT>point</TT>), the HTML label will be embedded within the node the
same way an ordinary label would be.
same way an ordinary label would be. Adding HTML labels to record-based shapes (record and Mrecord) is discouraged and may lead to unexpected behavior because of their conflicting label schemas and overlapping functionality.
<P>
The following is an abstract grammar for HTML labels.
Terminals, corresponding to elements, are shown in bold font,
......
......@@ -7,7 +7,7 @@ SUBDIRS = demo
TCLHANDLE_INCLUDES=-I$(top_srcdir)/tclpkg/tclhandle
TCLHANDLE_LIBS=$(top_builddir)/tclpkg/tclhandle/libtclhandle_C.la
if WITH_LIBGD
GDTCLFT_LIBS = $(top_srcdir)/tclpkg/gdtclft/libgdtclft_C.la
GDTCLFT_LIBS = $(top_builddir)/tclpkg/gdtclft/libgdtclft_C.la
endif
pdfdir = $(pkgdatadir)/doc/pdf
......