Mathematica 9 is now available
Services & Resources / Wolfram Forums
-----
 /
MathGroup Archive
2006
*January
*February
*March
*April
*May
*June
*July
*August
*September
*October
*November
*December
*Archive Index
*Ask about this page
*Print this page
*Give us feedback
*Sign up for the Wolfram Insider

MathGroup Archive 2006

[Date Index] [Thread Index] [Author Index]

Search the Archive

Re: Re: GraphPlot display anomaly


You were right about the double picture; there seems to be indeed an  
error in the package. (I failed to see this because once I saw the  
syntax of your program was wrong I did not pay any attention to its  
semantics).

Anyway, the problem can be overcome with a simple application of Block:

In[1]:=
Needs["DiscreteMath`GraphPlot`"];

In[2]:=
Show[Block[{$DisplayFunction=Identity},GraphPlot[{1 -> 2},
     ImageSize -> {50, 50}]]]

works fine, at least on my system.

Andrzej Kozlowski



On 27 Dec 2006, at 19:27, zac wrote:

> Well, not quite self-evident, since your answer only explains the
> question concerning the necessity of Evaluate. I do accept that I've
> left out the parenthesis, but this does not explain why there are two
> outputs in the notebook. Actually, as Chris wrote, it must be  
> something
> with a Block in the package. Does anyone know a method to overcome  
> this
> Block-problem?
>
> istvan
>
>
> Andrzej Kozlowski wrote:
>>
>> The only problem is with your code. The correct way to do this is:
>>
>>
>> Needs["DiscreteMath`GraphPlot`"];
>>
>>
>> GraphPlot[{1 -> 2},
>>      ImageSize -> {50, 50},
>>      DisplayFunction -> (Display[$Display, #] &)
>>      ];
>>
>> Note the crucial parentheses missing from original code.
>> I think the answers to all your questions should now be self-evident.
>>
>> Andrzej Kozlowski
>> Tokyo, Japan
>


  • Prev by Date: glibc version problem
  • Next by Date: Re: large input to NMinimize causes NMinimize:"bcons" along with Less:nord ... and I don't think it should
  • Previous by thread: Re: GraphPlot display anomaly
  • Next by thread: Re: GraphPlot display anomaly