The Loop Panel sample is very simple and is therefore not impacted much by the use of Drop Shadow Effect.
So why would we need a double value to act as an index into a collection?
Actually, only the whole portion of the Offset value is considered when determining the index of the pivotal child.
I had some extra time this weekend, so I refactored one of my early looping panels into something that might be useful for a wider audience.
This post also includes a simple demo showing how the Loop Panel can be used as the items host of a custom List Box class.
😉 This post is actually about supporting a very specific natural user interaction within an Items Control.
Microsoft Surface was first publicly unveiled a couple of years ago.
Okay, this post isn’t really about creating a full blown Natural User Interface (NUI)…
I just wanted to jump on the NUI bandwagon while it’s still the cool new thing!
(This just means a child can be whatever size it desires in the stacking direction, but it is constrained in the nonstacking direction.) To support these layout requirements, it was clear that I would need an property.
Of course, there are some key differences between a Loop Panel and a Stack Panel.
In the Loop Panel class, I wanted to support both a horizontal and vertical orientation, just as Stack Panel does.