> I agree. I think the current behaviour is ilogical (because [if] is a > code tag that should not add or delete anything to the XHTML by > itself) and creates layout problems. I had the same problem than you > and found the same solution than David, but formatting the source that > way makes it less readable. > > Maybe the [if] behaviour could change in future releases?
I think there may be some confusion here. The [if]statement does not output a line break, the problem is that you have a line break outside the [if] statement. It is, in my opinion, very logical indeed that the [if]statement should not under any circumstances affect things outside it's scope. If you do not like the way the code looks in the solution, may I suggest you use the escape character to remove the line break? It is what i usually do: [if ingroup foo] * Menu Item 1 * Menu Item 2[if]` [if ingroup bar] * Menu Item 3 * Menu Item 4[if]` should remove the line breaks (if i'm using the correct escape character, see the markup section if I'm not). This does a lot for readability, even if remembering all those escape characters can be annoying. However, this is a neccesary evil when you combine code and outputet text like this. Happy coding. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
