Am 27.04.2015 um 11:09 schrieb Jürgen Spitzmüller:
I inspected the (actually not so few) uses now, and I think that getString
and getDocString is the place where tabs should be replaced by blanks.
Doing it in eatLine breaks parsing of LANGUAGES.
See attached patch. Opinions?
Hi Jürgen,
since I don't know this code I cannot state on this. For me it important
to be able to use tabs for the spacing for all statements. This makes
working with the layouts and modules much easier.
If an author prefers spaces, it is OK but then all spacings should be
spaces. The mixture caused some troubles for me and that is why I
committed the whitespace change (I was not aware that a simple
whitespace fix causes these problems.)
Btw. I added a new module for PDF forms. This works great and I already
created several forms with it at work. However, it would be nice to have
the feature that the content of an Argument is passThru while another
one is not.
So what I want is e.g. this:
InsetLayout Flex:TextField
Argument 1
MenuString "PDF form parameters"
LabelString "Params"
Tooltip "Insert PDF form parameters here"
PassThru 1
EndArgument
PassThru 0
End
so that only the content of the argument is passthru while the content
of the flex inset is not.
It should also be possible to get the opposite (inset is passthru but
not argument) and also that one argument is passthru while a second
argument is not.
What do you think?
many thanks and best regards
Uwe
