Al 18/03/13 22:34, En/na Wolfgang Schuster ha escrit:

Am 18.03.2013 um 19:32 schrieb Xan :

...

Hi,

I found a possibly bug (I attached the doc). With bigskip twocolumns work but with \column it does not. That is, with the diff:

98c98 < \bigskip ---

...

%\bigskip 100c100 < %\column

---

...

\column

it does not work: the last exercise is shown in the first column.

The default value to fill the column (\vskip\textheight) does only work when you start the columns at the top of the page but not when you start them in the middle of page. When this fixed value is replaced with \pagegoal it does also work in the middle of the page.

% \installcolumnbreakmethod \s!multicolumn \v!yes % {\vskip\textheight % \penalty-200 % we can mark and intercept this % \vskip-\textheight}

\unprotect \installcolumnbreakmethod \s!multicolumn \v!yes {\vskip .5\pagegoal \penalty-200 % we can mark and intercept this \vskip-.5\pagegoal} \protect

\starttext

\startcolumns a \column b \stopcolumns

\page

\blank[force,12cm]

\startcolumns a \column b \stopcolumns

\stoptext

Wolfgang Can you modify it for working? By the user perspective it's an annoying bug. A clean command should not produce that, isn't it?

Xan.

On 3/20/2013 10:28 AM, Wolfgang Schuster wrote:

Am 19.03.2013 um 20:50 schrieb Xan :

...

Can you modify it for working? By the user perspective it's an annoying bug. A clean command should not produce that, isn't it?

I have to agree that the current situation with the \column command isn’t perfect but each solution has it’s own problems.

The example below uses three different definitions for the \column command, the first and third result in a empty column when there is to much text in the first column while the second definition ignores the command and balances the text of both columns.

<example> \starttext \showframe

% Default method

\blank[force,12cm]

\startcolumns \dorecurse{16}{a\par} \column b \stopcolumns

\page

% Method 1

\unprotected\installcolumnbreakmethod \s!multicolumn \v!yes {\scratchdimen\dimexpr\pagegoal/2\relax \vskip \scratchdimen \penalty-200 % we can mark and intercept this \vskip-\scratchdimen}

\blank[force,12cm]

\startcolumns \dorecurse{16}{a\par} \column b \stopcolumns

\page

% Method 2

\unprotected\installcolumnbreakmethod \s!multicolumn \v!yes {\scratchdimen\dimexpr\pagegoal/2+\lineheight\relax \vskip \scratchdimen \penalty-200 % we can mark and intercept this \vskip-\scratchdimen}

\blank[force,12cm]

\startcolumns \dorecurse{16}{a\par} \column b \stopcolumns

\stoptext </example>

For Wolfgangs eyes only: \installcolumnbreakmethod \s!multicolumn \v!yes {\penalty\c_page_mix_break_forced\relax} Maybe that one works ok. Hans -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Al 20/03/13 10:52, En/na Wolfgang Schuster ha escrit:

Am 20.03.2013 um 10:40 schrieb Hans Hagen :

...

For Wolfgangs eyes only:

\installcolumnbreakmethod \s!multicolumn \v!yes {\penalty\c_page_mix_break_forced\relax}

Maybe that one works ok. No it doesn’t work, the penalty is ignored and text from the first column appears in the second column because the columns are balanced.

Wolfgang

Thanks guys for trying to solve which I definitely tag as a bug ;-). It seems there is no faster solution but surely Hans will find one ;-) By the user perspective it's an annoying behaviour and I have to change manually the paragraphs (adding \{*}skip commands). I think you will find a solution at the end. It's too much technical discussion for me. I'm sorry I can't do anything else. But I'm glad to see this discussion.... (so mantain me as CC) If I could do anything, please say to me. Thanks, Xan.

Al 21/03/13 23:58, En/na Wolfgang Schuster ha escrit:

Am 21.03.2013 um 09:40 schrieb Xan :

...

Thanks guys for trying to solve which I definitely tag as a bug ;-). It seems there is no faster solution but surely Hans will find one ;-) By the user perspective it's an annoying behaviour and I have to change manually the paragraphs (adding \{*}skip commands). I think you will find a solution at the end. It's too much technical discussion for me. I'm sorry I can't do anything else. But I'm glad to see this discussion.... (so mantain me as CC)

If I could do anything, please say to me. Can you test your example with the mixedcolumns environment instead of the normal columns environment (use the latest beta).

Wolfgang Yes, ofcourse. But what steps I have to do for that. I'm running context minimals (I don't know if stable or beta).

Thanks, Xan.

Al 21/03/13 23:58, En/na Wolfgang Schuster ha escrit:

Am 21.03.2013 um 09:40 schrieb Xan :

...

Thanks guys for trying to solve which I definitely tag as a bug ;-). It seems there is no faster solution but surely Hans will find one ;-) By the user perspective it's an annoying behaviour and I have to change manually the paragraphs (adding \{*}skip commands). I think you will find a solution at the end. It's too much technical discussion for me. I'm sorry I can't do anything else. But I'm glad to see this discussion.... (so mantain me as CC)

If I could do anything, please say to me. Can you test your example with the mixedcolumns environment instead of the normal columns environment (use the latest beta).

Wolfgang Now I have the beta context version. Now I want to use in my example mixedcolumns. But nothing in the wiki is present of how to work mixedcolumns.

Xan.

OOOppppsss! Do I have to kill myself! ;-))) Would like to have a reference for this kind of stuff! regards Keith. Am 20.03.2013 um 10:40 schrieb Hans Hagen :

For Wolfgangs eyes only:

\installcolumnbreakmethod \s!multicolumn \v!yes {\penalty\c_page_mix_break_forced\relax}

Maybe that one works ok.