2015-04-27 23:00 GMT+02:00 Uwe Stöhr: > 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.) >
My neither. You uncovered a bug. As to the whitespace, I prefer (2) spaces for intending sub-tags. This is also what most layouts use. I would propose: tabs for option-value separation, spaces for intendation of sub-tags. As soon as the getString methods are fixed, we can also use tabs for Requires and friends. > > 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? > It's a good enhancement, which I have somewhere on my list, but it is not easy to implement. Jürgen > > many thanks and best regards > Uwe >
