ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Jan-Erik Hägglöf" <janerik.hagglof@bredband.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: customized item list symbol/graphic
Date: Sat, 11 Dec 2010 14:27:00 +0100	[thread overview]
Message-ID: <4D037C24.8030703@bredband.net> (raw)

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

HI All Contexters out there!

I'm a Guy from sweden who will appreciate a possible solution to 
following problem.

I'm interested in to do a personalized itemlist with a symbol created in 
metapost.

Here is an example:

\startuniqueMPgraphic{square}
draw roundedsquare(20,20,2) withrgbcolor (.625,0,0);
\stopuniqueMPgraphic

\defineoverlay[square][\uniqueMPgraphic{square}]

\setupitemgroup
     [itemize]
     [1]
     [symbol=square]

\starttext


\startitemize[1,columns]
\dorecurse{10}{\item itempoint \par}
\stopitemize

\stoptext

This doesn't have any effect so my question is how do I manage this?

I did following as an alternative solution and it worked as I wanted but 
If I run this example the linebreak comes in to the next column(third 
item), which is not what I want. See example below!

\definedescription
    [task]
    [text=\uniqueMPgraphic{square}, width=broad]

\startcolumns
\dorecurse{5}{\task very long sentence i will now write to create this 
weird issue \par}
\stopcolumns



How do I prevent this, or is there a better solution?

Many thanks in advance

Janneman

[-- Attachment #2: test.tex --]
[-- Type: text/x-tex, Size: 596 bytes --]

\startuniqueMPgraphic{square}
draw roundedsquare(20,20,2) withrgbcolor (.625,0,0);
\stopuniqueMPgraphic

\defineoverlay[square][\uniqueMPgraphic{square}]

\definedescription
   [task]
   [text=\uniqueMPgraphic{square}, width=broad]

\setupitemgroup
    [itemize]
    [1]
    [symbol=square]

\starttext

\section {First try to change symbol}
\startitemize[1,columns]
\dorecurse{10}{\item itempoint \par}
\stopitemize

\section {Next try to define an own description}

\startcolumns
\dorecurse{5}{\task very long sentence i will now write to create this weird issue \par}
\stopcolumns

\stoptext


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

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2010-12-11 13:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-11 13:27 Jan-Erik Hägglöf [this message]
2010-12-11 13:42 ` Taco Hoekwater
2010-12-11 14:37   ` Jan-Erik Hägglöf
2010-12-11 15:23     ` Wolfgang Schuster
2010-12-11 16:14       ` Jan-Erik Hägglöf
2010-12-11 17:22         ` Jan-Erik Hägglöf
2010-12-11 17:24         ` Wolfgang Schuster
2010-12-11 17:39           ` customized item list symbol/graphic [solved] Jan-Erik Hägglöf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D037C24.8030703@bredband.net \
    --to=janerik.hagglof@bredband.net \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).