Figure [left]

Figure [left]

[David Arnold]

[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]

All,

Both this:

%output=pdf

\starttext

We use the notation $(2,4)$ to denote what is called an {\em ordered
   pair}. If you think of the positions taken by
\placefigure
[left][fig:ordpair]
{}{\externalfigure[section1figs-mpgraph.1]}
ordered pairs $(4,2)$ and $(2,4)$ in the coordinate plane
(see \in{Figure}[fig:ordpair]), then it is immediately apparent why
order is important. The ordered pair $(4,2)$ is simply not the same as
the ordered pair $(2,4)$.

\stoptext

And this:

%output=pdf

\starttext

We use the notation $(2,4)$ to denote what is called an {\em ordered
   pair}. If you think of the positions taken by
\placefigure
[left][fig:ordpair]
{}{\externalfigure[section1figs-mpgraph.1]}
ordered pairs $(4,2)$ and $(2,4)$ in the coordinate plane
(see \in{Figure}[fig:ordpair]), then it is immediately apparent why
order is important. The ordered pair $(4,2)$ is simply not the same as
the ordered pair $(2,4)$.

\stoptext

Lead to the same attached result. This is not the behavior expected.  
Any ideas?


[-- Attachment #2: section1figs-mpgraph.1 --]
[-- Type: application/octet-stream, Size: 2972 bytes --]

%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: -9 -11 82 83 
%%HiResBoundingBox: -8.853 -10.7044 81.65207 82.47198 
%%Creator: MetaPost 0.901
%%CreationDate: 2006.03.21:1720
%%Pages: 1
%%DocumentFonts: CMMI12 CMR12
%%BeginProlog
 /cmmi12 /CMMI12 def
 /cmr12 /CMR12 def
/fshow {exch findfont exch scalefont setfont show}bind def
%%EndProlog
%%Page: 1 1
%%HiResBoundingBox: -8.853 -10.7044 81.65207 82.47198
 0.85 setgray 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth
 [] 0 setdash 1 setlinecap 1 setlinejoin 10 setmiterlimit
newpath 0 0 moveto
0 71.99997 lineto stroke
 0 0.5 dtransform truncate idtransform setlinewidth pop
newpath 0 0 moveto
71.99997 0 lineto stroke
 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth
newpath 14.4 0 moveto
14.4 71.99997 lineto stroke
 0 0.5 dtransform truncate idtransform setlinewidth pop
newpath 0 14.4 moveto
71.99997 14.4 lineto stroke
 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth
newpath 28.79999 0 moveto
28.79999 71.99997 lineto stroke
 0 0.5 dtransform truncate idtransform setlinewidth pop
newpath 0 28.79999 moveto
71.99997 28.79999 lineto stroke
 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth
newpath 43.19998 0 moveto
43.19998 71.99997 lineto stroke
 0 0.5 dtransform truncate idtransform setlinewidth pop
newpath 0 43.19998 moveto
71.99997 43.19998 lineto stroke
 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth
newpath 57.59998 0 moveto
57.59998 71.99997 lineto stroke
 0 0.5 dtransform truncate idtransform setlinewidth pop
newpath 0 57.59998 moveto
71.99997 57.59998 lineto stroke
 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth
newpath 71.99997 0 moveto
71.99997 71.99997 lineto stroke
 0 0.5 dtransform truncate idtransform setlinewidth pop
newpath 0 71.99997 moveto
71.99997 71.99997 lineto stroke
 0 setgray
newpath 0 0 moveto
71.99997 0 lineto stroke
newpath 68.30437 -1.5308 moveto
71.99997 0 lineto
68.30437 1.5308 lineto
 closepath
gsave fill grestore stroke
 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth
newpath 0 0 moveto
0 71.99997 lineto stroke
 0 0.5 dtransform truncate idtransform setlinewidth pop
newpath 1.5308 68.30437 moveto
0 71.99997 lineto
-1.5308 68.30437 lineto
 closepath
gsave fill grestore stroke
74.99997 -2.5737 moveto
(x) cmmi12 11.95517 fshow
-3.0683 77.32458 moveto
(y) cmmi12 11.95517 fshow
69.07347 -10.7044 moveto
(5) cmr12 11.95517 fshow
-8.853 68.14777 moveto
(5) cmr12 11.95517 fshow
30.89998 62.68877 moveto
(\(2) cmr12 11.95517 fshow
41.30528 62.68877 moveto
(;) cmmi12 11.95517 fshow
46.54948 62.68877 moveto
(4\)) cmr12 11.95517 fshow
 0 3 dtransform truncate idtransform setlinewidth pop
newpath 28.79999 57.59998 moveto 0 0 rlineto stroke
29.44519 17.7336 moveto
(\(4) cmr12 11.95517 fshow
39.8505 17.7336 moveto
(;) cmmi12 11.95517 fshow
45.0947 17.7336 moveto
(2\)) cmr12 11.95517 fshow
newpath 57.59998 28.79999 moveto 0 0 rlineto stroke
showpage
%%EOF

[-- Attachment #3: Type: text/plain, Size: 2 bytes --]




[-- Attachment #4: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: Figure [left]

[Aditya Mahajan]

<--- On Mar 21, David Arnold wrote --->

> All,
>
> Both this:
>
> %output=pdf
>
> \starttext
>
> We use the notation $(2,4)$ to denote what is called an {\em ordered
> pair}. If you think of the positions taken by
> \placefigure
> [left][fig:ordpair]
> {}{\externalfigure[section1figs-mpgraph.1]}
> ordered pairs $(4,2)$ and $(2,4)$ in the coordinate plane
> (see \in{Figure}[fig:ordpair]), then it is immediately apparent why
> order is important. The ordered pair $(4,2)$ is simply not the same as
> the ordered pair $(2,4)$.
>
> \stoptext
>
> And this:
>
> %output=pdf
>
> \starttext
>
> We use the notation $(2,4)$ to denote what is called an {\em ordered
> pair}. If you think of the positions taken by
> \placefigure
> [left][fig:ordpair]
> {}{\externalfigure[section1figs-mpgraph.1]}
> ordered pairs $(4,2)$ and $(2,4)$ in the coordinate plane
> (see \in{Figure}[fig:ordpair]), then it is immediately apparent why
> order is important. The ordered pair $(4,2)$ is simply not the same as
> the ordered pair $(2,4)$.
>
> \stoptext
>
> Lead to the same attached result. This is not the behavior expected. Any 
> ideas?

I am not sure on what you want to achieve, but does this look better?

\starttext
\placefigure
[left][fig:ordpair]
{}{\externalfigure[section1figs-mpgraph.1]}
We use the notation $(2,4)$ to denote what is called an {\em ordered
   pair}. If you think of the positions taken by
  ordered pairs $(4,2)$ and $(2,4)$ in the coordinate plane
  (see \in{Figure}[fig:ordpair]), then it is immediately apparent why
  order is important. The ordered pair $(4,2)$ is simply not the same 
as
  the ordered pair $(2,4)$.

  \stoptext


HTH,
Aditya

-- 
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008

Re: Figure [left]

[Matthias Weber]

I don't know either what the goal is, when I want to place a figure  
left to the text
I use \startfiguretext etc.

Matthias


On Mar 21, 2006, at 9:18 PM, Aditya Mahajan wrote:

> <--- On Mar 21, David Arnold wrote --->
>
>> All,
>>
>> Both this:
>>
>> %output=pdf
>>
>> \starttext
>>
>> We use the notation $(2,4)$ to denote what is called an {\em ordered
>> pair}. If you think of the positions taken by
>> \placefigure
>> [left][fig:ordpair]
>> {}{\externalfigure[section1figs-mpgraph.1]}
>> ordered pairs $(4,2)$ and $(2,4)$ in the coordinate plane
>> (see \in{Figure}[fig:ordpair]), then it is immediately apparent why
>> order is important. The ordered pair $(4,2)$ is simply not the  
>> same as
>> the ordered pair $(2,4)$.
>>
>> \stoptext
>>
>> And this:
>>
>> %output=pdf
>>
>> \starttext
>>
>> We use the notation $(2,4)$ to denote what is called an {\em ordered
>> pair}. If you think of the positions taken by
>> \placefigure
>> [left][fig:ordpair]
>> {}{\externalfigure[section1figs-mpgraph.1]}
>> ordered pairs $(4,2)$ and $(2,4)$ in the coordinate plane
>> (see \in{Figure}[fig:ordpair]), then it is immediately apparent why
>> order is important. The ordered pair $(4,2)$ is simply not the  
>> same as
>> the ordered pair $(2,4)$.
>>
>> \stoptext
>>
>> Lead to the same attached result. This is not the behavior  
>> expected. Any
>> ideas?
>
> I am not sure on what you want to achieve, but does this look better?
>
> \starttext
> \placefigure
> [left][fig:ordpair]
> {}{\externalfigure[section1figs-mpgraph.1]}
> We use the notation $(2,4)$ to denote what is called an {\em ordered
>    pair}. If you think of the positions taken by
>   ordered pairs $(4,2)$ and $(2,4)$ in the coordinate plane
>   (see \in{Figure}[fig:ordpair]), then it is immediately apparent why
>   order is important. The ordered pair $(4,2)$ is simply not the same
> as
>   the ordered pair $(2,4)$.
>
>   \stoptext
>
>
> HTH,
> Aditya
>
> -- 
> Aditya Mahajan, EECS Systems, University of Michigan
> http://www.eecs.umich.edu/~adityam || Ph: 7342624008
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context

Re: Figure [left]

[David Arnold]

[-- Attachment #1.1: Type: text/plain, Size: 2140 bytes --]

Aditya,

Thanks, this worked.

On Mar 21, 2006, at 6:18 PM, Aditya Mahajan wrote:

> <--- On Mar 21, David Arnold wrote --->
>
> > All,
> >
> > Both this:
> >
> > %output=pdf
> >
> > \starttext
> >
> > We use the notation $(2,4)$ to denote what is called an {\em ordered
> > pair}. If you think of the positions taken by
> > \placefigure
> > [left][fig:ordpair]
> > {}{\externalfigure[section1figs-mpgraph.1]}
> > ordered pairs $(4,2)$ and $(2,4)$ in the coordinate plane
> > (see \in{Figure}[fig:ordpair]), then it is immediately apparent why
> > order is important. The ordered pair $(4,2)$ is simply not the  
> same as
> > the ordered pair $(2,4)$.
> >
> > \stoptext
> >
> > And this:
> >
> > %output=pdf
> >
> > \starttext
> >
> > We use the notation $(2,4)$ to denote what is called an {\em ordered
> > pair}. If you think of the positions taken by
> > \placefigure
> > [left][fig:ordpair]
> > {}{\externalfigure[section1figs-mpgraph.1]}
> > ordered pairs $(4,2)$ and $(2,4)$ in the coordinate plane
> > (see \in{Figure}[fig:ordpair]), then it is immediately apparent why
> > order is important. The ordered pair $(4,2)$ is simply not the  
> same as
> > the ordered pair $(2,4)$.
> >
> > \stoptext
> >
> > Lead to the same attached result. This is not the behavior  
> expected. Any
> > ideas?
>
> I am not sure on what you want to achieve, but does this look better?
>
> \starttext
> \placefigure
> [left][fig:ordpair]
> {}{\externalfigure[section1figs-mpgraph.1]}
> We use the notation $(2,4)$ to denote what is called an {\em ordered
>    pair}. If you think of the positions taken by
>   ordered pairs $(4,2)$ and $(2,4)$ in the coordinate plane
>   (see \in{Figure}[fig:ordpair]), then it is immediately apparent why
>   order is important. The ordered pair $(4,2)$ is simply not the same
> as
>   the ordered pair $(2,4)$.
>
>   \stoptext
>
>
> HTH,
> Aditya
>
> -- 
> Aditya Mahajan, EECS Systems, University of Michigan
> http://www.eecs.umich.edu/~adityam || Ph: 7342624008
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>


[-- Attachment #1.2: Type: text/html, Size: 4220 bytes --]

[-- Attachment #2: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context