Re: [Boost-users] graphviz compile problem

From: Doug Gregor (dgregor_at_[hidden])
Date: 2004-12-15 16:00:50

On Dec 3, 2004, at 2:30 PM, Jean Utke wrote:

> Hi Doug,
>
> thanks for your reply.
> I do need to remove vertices/edges, hence the listS.
> There is  the issue of dot not parsing hex addresses properly and I 
> understand the reason for changing the code in this respect.
> I can add the additional property to all my graphs but that is 
> overhead for me since I use the graphviz stuff for debugging only.
> Rather than incurring that overhead I would prefer
> to filter the hex addresses to dot-readable names and not print any  
> labels. If people want to see their vertices indexed and printed like
> this they can add the vertex_index property and write their own label 
> writers.
> Is there any chance for a graphviz code change that filters the hex 
> addresses ?

I don't believe that filtering the hex addresses is a good solution in 
general, because we don't have any idea what the output of a given 
vertex descriptor will look like. So, I've added a new final parameter 
to write_graphviz that maps from vertex descriptors to an ID that can 
be used by GraphViz. This property map defaults to get(vertex_index, g) 
(so that old behavior does not change), but you can override it to use 
a (cleaned-up) hex address or anything else. I hope that helps.

The fix, with documentation of course, is now in Boost CVS.

        Doug