You are correct, that this could be a bit unexpected. But it is still probably related to the extra line inserted when the condition fails--because that extra line causes BoltWire to behave differently. The problem is, in trying to get BoltWire to act intuitively with the linespacing, we have to get it to try and guess my intentions. Which it can only approximate. Sometimes it gets it wrong.
In the next release there will be a way to disable the adding of extra lines to a zone, by simply capitalizing the zone marker. IE [[HEADER]] vs [[header]]. That may solve the problem for you, but you'll have to wait till I get the release out. That will give you some control over this Please see my post to Kevin where I discussed this issue in great detail... http://groups.google.com/group/boltwire/browse_thread/thread/9da39d02b72be77b In the mean time you might just put the line return inside the if statements and it should improve things for you. At some point we may come up with a better way of identifying paragraphs, but it's quite tricky. As you know from all the tinkering we've had to do to get even this functionalality! Cheers, Dan On Wed, Nov 25, 2009 at 1:47 PM, Markus <[email protected]> wrote: > On Nov 25, 2:06 pm, The Editor <[email protected]> wrote: >> On Tue, Nov 24, 2009 at 2:09 PM, Markus <[email protected]> wrote: >> >> > The goal should be that no if-hacks are needed like this one: >> >> > [if whatever]...[if][if whatelse] >> > here I need the line break but not that huge white space (see above) >> > when whatelse is false[if] >> >> It looks like you are getting exactly what is expected. If you put the >> line return outside the [if whatever] [if] then it will appear whether >> the condition is passed or not. If you want the line return to only >> appear when the condition is met, you need to put it inside the >> conditional. It is simply a question of seeing the actual line return. >> In your example it is **after** the closing [if]. >> >> Though this issue has come up before, I think it is much more a hack, >> and even counter-intuitive to extend the conditional to a line break >> that follows or precedes the if wrappers. In other words, the if >> statement's are behaving very literally, and in my view doing exactly >> what they should be doing. > > I am fine with the if statements behaving literally. Actually my > problem has nothing to do with if statements. :) > > The code I use is: > ! [[some.page|[^some_pic.png^]]][[some.page|Some title]] > [if* equal {member} Markus]$$actions[if*] > > Consider being logged out. Then the second line is just an empty one. > So we get: > > ! Heading > *empty line* > > And that empty line produces this code: > > <div class='vspace'> </div> > <br /> > > Is this really what you expect? I understand that the empty line is > not treated as a paragraph because there is no line break to end it. > So far, so good. But if there is not even a paragraph why is there > vertical space plus a line break? > > In this case, I only expected the heading without any white space > beneath. > > If you end a paragraph by an empty line, you won't get vspace and a br > inserted I guess (and hope). The same should go for headings and > similar stuff. > > Regards, Markus > >> >> Cheers, >> Dan > > -- > > You received this message because you are subscribed to the Google Groups > "BoltWire" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/boltwire?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/boltwire?hl=en.
