Unfortunately, Maple 12 is my go to version.  15 is not readily available for me and with 15 being the go to versions of choice for many users now, I'll probably be hardpressed to get many users to bother tackling the problem.  At least I know it works in 15.

I understand that a lot of improvements/enhancements were done to the HTTP package since 12 and that was probably one of them.  If it is a bug, I might be stuck.  Usually a workaround exists ... hopefully?

@Robert Israel just to confirm it works I had access to Maple 15 but for users of Maple 12 there is a subs bug that doesn't allow the substitution.

@Robert Israel just to confirm it works I had access to Maple 15 but for users of Maple 12 there is a subs bug that doesn't allow the substitution.

We could circumvent the issue Maple is having with a small proc so we don't have to keep redefining the graph

DrawGraph2 := proc (G, p) #specific to tree style structures
  uses GraphTheory:
  DrawGraph(Graph(undirected, G), style = tree, root = p)
end proc:

DrawGraph2({{2, 3}, {2, 4}, {3, 5}}, 3)

            3
         /     \
       2       5
       |
      4

We could circumvent the issue Maple is having with a small proc so we don't have to keep redefining the graph

DrawGraph2 := proc (G, p) #specific to tree style structures
  uses GraphTheory:
  DrawGraph(Graph(undirected, G), style = tree, root = p)
end proc:

DrawGraph2({{2, 3}, {2, 4}, {3, 5}}, 3)

            3
         /     \
       2       5
       |
      4

It must be the internet connection program I use that doesn't support the operations.

Not exactly sure what you mean. 

Not exactly sure what you mean. 

Actually I don't thinik that is what you want, you could try DrawGraph from the GraphTheory package.

Actually I don't thinik that is what you want, you could try DrawGraph from the GraphTheory package.

@Alejandro Jakubi 

Here's my reason.  I was in Typesetting:extended mode.  In your example %A doesn't work with typesetting set to extended but %a does.  That was before I found the bug in extended mode for coloring.  Then I posted the typesetting extended bug and this morning saw your message that you meant %A not %a.  So I tried it again and %A didn't work so .. I thought maybe typesetting is the problem, so I checked to see if it had an effect and in fact it does. 

@Alejandro Jakubi 

Here's my reason.  I was in Typesetting:extended mode.  In your example %A doesn't work with typesetting set to extended but %a does.  That was before I found the bug in extended mode for coloring.  Then I posted the typesetting extended bug and this morning saw your message that you meant %A not %a.  So I tried it again and %A didn't work so .. I thought maybe typesetting is the problem, so I checked to see if it had an effect and in fact it does. 

@Alejandro Jakubi 

I think you meant to write
nprintf("#mo(%a,mathcolor=\"%A\")", s, c)

The first `a` being lower case instead of upper case.

@Alejandro Jakubi 

I think you meant to write
nprintf("#mo(%a,mathcolor=\"%A\")", s, c)

The first `a` being lower case instead of upper case.

Thanks for the alternates, gives me a better understanding of the undocumented code.

I read Paulina's argument on the subject.

pchine wrote : "... other Maplesoft staff will set up polls or discussion questions elsewhere on MaplePrimes asking for input"

That is an old post but poll questions no longer exist on mapleprimes - a loss, perhaps, but those are fuzzy logic information gathering tools.  A probability based directional approach, they are helpful and should be re-implemented on mapleprimes.

Discussion questions from Maplesoft, I find are fairly few but I suppose enough outside information is gathered based on the questions that arise here on mapleprimes.  That is passive information gathering.  Aside from posting discussion questions how else (may I ask?) is Maplesoft gathering information through the `active information gathering` route?    although they probably have enough passive information to deal with.

pchin wrote : "... we are not expecting a structure like `#mi( "V" )` to be generated by a user."

I think that statement was clarified, but if a structure can be used in Maple then it should be documented regardless of whether someone may or may not be expected to use it.  Murphys Law comes to mind, if you think someone might use it but most likely won't, then it is most probable that they will.