image-layout | deterministic image layout algorithms written in pure | Computer Vision library

I'm not quite sure which library you use for this so I couldn't test it. But my guess is that you first need a dictionary Item or 2. You have to iterate over the first data array and then over the underlying data array in the relationships/stages object. Something like this should work:

Contextualize() sets the ViewContext property of the IHtmlHelper where method is called on. Strictly speaking your not contextualizing the tag helper, just the HtmlHelper.

The ViewContext encapsulates all information about the current view being executed as well as the currently executing action (as ViewContext derives from ActionContext). Most of the HtmlHelper methods depends on ViewContext being set: such as methods generating action links as it contains route data or for keeping state when rendering a form.

MVC will automatically call Contextualize on the the HTML helper (in fact, on all IViewContextAware implementations) for when executing a regular Razor view. The HtmlHelper is not a default concept for tag helpers however. When you inject it through the constructor of the tag helper, it will create a new instance which is not "contextualized" with any view information. Therefore you have to call it manually.

An exception will be thrown when a method which requires the ViewContext to be set is called.

tl;dr: always call Contextualize when injecting IHtmlHelper in your tag helper or it won't function properly.

There were a couple of issues. It was not exactly a ng-style problem, but rather than in each digest cycle your photos were calculating different style objects, causing another digest cycle to run.

Some issues I've found:

• Error in logic was giving 0 colums, thus causing size to give NaN when calculating margin-top and failing. To fix this, I added a default value from 1 column.
• your Math.random() > 0.8 was giving different results in each time your filter function was executing. In each digest cycle, since Math.random() gives different results, it was forcing another digest loop (you were updating gridSize object - since there's a $watch for each element in the ng-repeat it detects the changes and forces one digest cycle), and so on. That was the error log in console.

I created this fiddle that works. The main changes are

defined a fixed random value for each photo, after declaring your array