Re: [NTG-context] project structure (bug?)
Am 08.02.2008 um 18:19 schrieb Hans Hagen: > Steffen Wolfrum wrote: > >> Why does this make a difference? > > see taco's answer; the layout is synchronized at certain points (those > where dimensions may need recalculation), so any change can be made > undone by this automatism; just use the setups to change your settings Ah, down there it is! Thanks, found it. % However, we will use setups: % to be documented ... yes, glorious day when all this will be finally documented ,o) Steffen ___ 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] project structure (bug?)
Steffen Wolfrum wrote: > Why does this make a difference? see taco's answer; the layout is synchronized at certain points (those where dimensions may need recalculation), so any change can be made undone by this automatism; just use the setups to change your settings Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] project structure (bug?)
Am 08.02.2008 um 17:19 schrieb Taco Hoekwater:
> Steffen Wolfrum wrote:
>> Am 08.02.2008 um 16:58 schrieb Taco Hoekwater:
>>
>>>
>>> Steffen Wolfrum wrote:
Hi,
does it make sense that eg
\clubpenalty=1
doesn't work when written in a project's environment file?
>>> I think so, yes (technically it is a side-effect).
>>>
>>> This should work even in the environment file:
>>>
>>>\def\defaultclubpenalty {1}
>>>\setdefaultpenalties
>>
>>
>>
>> And all of them like this?
>>
>> \def\defaultclubpenalty {1}
>> \def\defaultwidowpenalty {1}
>> \def\defaultdisplaywidowpenalty {1}
>> \def\defaultbrokenpenalty {0}
>>
>> \setdefaultpenalties
>>
>>
>> I experienced also very interesting differences between setting in
>> environment file \setuplayout[grid=no] and in component \setuplayout
>> [grid=yes]
>> compared to setting in environment file \setuplayout[grid=yes] .
>>
>> As working with grid is in itself quite fragile (and surprising) I
>> guess this is not explainable / avoidable?
>
>
> grid mode has a separate set of defaults, yes. See core-spa.tex
> (easier for me than writing it all down)
What about the difference in writing in
environment file \setuplayout[grid=no] plus in component \setuplayout
[grid=yes]
compared to setting in environment file \setuplayout[grid=yes]
Why does this make a difference?
Steffen
___
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] project structure (bug?)
Steffen Wolfrum wrote:
> Am 08.02.2008 um 16:58 schrieb Taco Hoekwater:
>
>>
>> Steffen Wolfrum wrote:
>>> Hi,
>>>
>>> does it make sense that eg
>>>
>>> \clubpenalty=1
>>>
>>> doesn't work when written in a project's environment file?
>> I think so, yes (technically it is a side-effect).
>>
>> This should work even in the environment file:
>>
>>\def\defaultclubpenalty {1}
>>\setdefaultpenalties
>
>
>
> And all of them like this?
>
> \def\defaultclubpenalty {1}
> \def\defaultwidowpenalty {1}
> \def\defaultdisplaywidowpenalty {1}
> \def\defaultbrokenpenalty {0}
>
> \setdefaultpenalties
>
>
> I experienced also very interesting differences between setting in
> environment file \setuplayout[grid=no] and in component \setuplayout
> [grid=yes]
> compared to setting in environment file \setuplayout[grid=yes] .
>
> As working with grid is in itself quite fragile (and surprising) I
> guess this is not explainable / avoidable?
grid mode has a separate set of defaults, yes. See core-spa.tex
(easier for me than writing it all down)
Best wishes,
Taco
___
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] project structure (bug?)
Am 08.02.2008 um 16:58 schrieb Taco Hoekwater:
>
>
> Steffen Wolfrum wrote:
>> Hi,
>>
>> does it make sense that eg
>>
>> \clubpenalty=1
>>
>> doesn't work when written in a project's environment file?
>
> I think so, yes (technically it is a side-effect).
>
> This should work even in the environment file:
>
>\def\defaultclubpenalty {1}
>\setdefaultpenalties
And all of them like this?
\def\defaultclubpenalty {1}
\def\defaultwidowpenalty {1}
\def\defaultdisplaywidowpenalty {1}
\def\defaultbrokenpenalty {0}
\setdefaultpenalties
I experienced also very interesting differences between setting in
environment file \setuplayout[grid=no] and in component \setuplayout
[grid=yes]
compared to setting in environment file \setuplayout[grid=yes] .
As working with grid is in itself quite fragile (and surprising) I
guess this is not explainable / avoidable?
Thanks,
Steffen
___
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] project structure (bug?)
Steffen Wolfrum wrote:
> Hi,
>
> does it make sense that eg
>
> \clubpenalty=1
>
> doesn't work when written in a project's environment file?
I think so, yes (technically it is a side-effect).
This should work even in the environment file:
\def\defaultclubpenalty {1}
\setdefaultpenalties
Best wishes,
Taco
___
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] project structure (bug?)
Hi, does it make sense that eg \clubpenalty=1 doesn't work when written in a project's environment file? It must be repeated at top of each single component in order to work. I am wondering what else works only when written in component (and is silently ignored although written in my environment-file) ... Steffen ___ 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
