Thanks much for tracking this down, Matt.

On Sun, Oct 9, 2011 at 7:01 PM, Matt Jones <[email protected]> wrote:

>
> On Oct 7, 2011, at 12:12 PM, Bob Sleys wrote:
>
> > This issue keeps cropping in up many forms.  Here is my latest issue that
> I don't have a workaround for yet. Basically I'm looping though a scoped set
> of data building a text string I then want to pass though Redcloth to
> display in a div tag.  the problem is all the results of the <% %> code it
> being output into the html which isn't right only code with <%= %> should
> result in output.  In the end I end up with a my text in the div tag twice,
> once for when the temp string in build and then again for when it's passed
> though RedCloth.  Code below for reference.  Highlighted code should not
> result in output to the page, but currently does.  Note this worked in
> previous hobo builds fine.
> >
> > app/views/floors/show.dryml
> >
> > <show-page>
> >   <content-body: >
> >     <div id="controls">
> >       <%=image_tag "cursors/zoom-in.png", :onmousedown => "map.zoom(1.25,
> 400, 300)" %><br/>
> >       <%=image_tag "cursors/zoom-out.png",:onmousedown => "map.zoom(0.75,
> 400, 300)" %>
> >     </div>
> >     <canvas id="floorplan" width="800" height="600" ></canvas>
> >     <div class="info" id="info">Mouse over markers on drawing to see
> additional info<br/>Shift Click on map to
> >       lock/unlock info.
> >     </div>
> >     <repeat with="&@positive_spaces">
> >       <div class="info" id="#{this.space_dwgid}" style="display: none;">
> >         <% t = "*#{this.name}*" %>
> >         <repeat with="&this.locations">
> >           <% t << "\n#{this.name} contains" %>
> >           <repeat with="&this.materials">
> >             <% t << "\n#{this.name} positive for "%>
> >             <repeat with="&this.samples">
> >               <% t << "#{this.sample_type} "%>
> >             </repeat>
> >           </repeat>
> >         </repeat>
>
> I *think* I've got this fixed now. There's a lot of confusing code
> revolving around new_context, which has two different places to tap the
> output (from the buffer and from the return value of the block). I've left a
> scrap of debug code in for the moment; any reports of DRYML code that dumps
> a line like this:
>
> new_context: /some/backtrace/path:42
>
> would be GREATLY appreciated. I'm also going to start working on a full-on
> DRYML test suite, as there are way more corner-cases than I would have
> believed possible...
>
> --Matt Jones
>
> --
> You received this message because you are subscribed to the Google Groups
> "Hobo Users" 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/hobousers?hl=en.
>
>


-- 
Owen Dall, Chief Systems Architect
Barquin International
www.barquin.com
Cell: 410-991-0811

-- 
You received this message because you are subscribed to the Google Groups "Hobo 
Users" 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/hobousers?hl=en.

Reply via email to