fluidkit Work Item Rss Feed

Commented Issue: Coverflow Loading Time [9474]

schungx — Fri, 29 Jun 2012 02:26:46 GMT

I am using coverflow in an application but it takes a considerable amount of time to load the pictures - when loading is finished then it works without any problem

The pictures are sent through an absolute url and are of about 1 mb each - end result will be displayed on a HD screen so high def pictures are required
Comments: ** Comment from web user: schungx **

Based on my experience, you can load up to around 50 items before the time lag gets noticeable. Mind you, that's 50 items in your collection, including the ones not visible on screen. Of course, if you have a slow CPU, or a very high-res screen but without a top GPU, then it may be slower.

If you add the items one by one asynchronously, then it will be much smoother, and you get a nice animation as each new item is added to the list. However, changing the selection and moving all the items will start to get slow as you have more items.

If the images are large, or come from a slow source (e.g. over the Internet), then you'll need to consider loading them asynchronously. Many times even if you turn on async loading in the Image class, it still goes through the UI thread. Try something like PriorityBinding to alleviate this problem.

- Stephen

Commented Issue: Coverflow Loading Time [9474]

exorgroup — Wed, 27 Jun 2012 19:46:04 GMT

thanks for the info - did you do some testing on how many pictures can be loaded and the size of each picture before UI hogging comes into play?

my reason for my question is that I am working with a very large screen therefore I have more room available which normally leads to having more visible pictures on the coverflow

Commented Issue: Coverflow Loading Time [9474]

schungx — Wed, 27 Jun 2012 09:49:57 GMT

You need more than the standard ElementFlow has to offer. You need virtualization of the container (only load items that are in sight) and async loading (load large pictures asynchronously so that it doesn't hog the UI thread).

Created Issue: Coverflow Loading Time [9474]

exorgroup — Tue, 26 Jun 2012 23:11:54 GMT

Created Issue: Coverflow Performance [8838]

Pat781 — Fri, 21 Oct 2011 06:13:28 GMT

Hello, I'm using the ElementFlow control for cover flow. I've found out, that if I use the ItemsSource with a CollectionViewSource and approximately 100 elements, the performance will be very low.

Regards,
Patrick

Created Issue: TransitionPresenter.ApplyTransition() fails at first call, if the presenter is on an not visible Tabpage [8060]

Wekalum — Sun, 27 Mar 2011 19:31:52 GMT

i have placed the TransitionPresenter on a TabControl. When my Application starts, that Tabpage is not the first one. But I have a control, which calls Presenter.ApplyTransition() in Reaction of changes of its DataContext.
In that particular case an error occurs, because .ApplyTransition() is called before the OnApplyTemplate() - override has initialized the internal TransitionContainer

Created Issue: Balloondecorator thickness [7547]

thurbo — Tue, 16 Nov 2010 18:33:33 GMT

In the Balloondecorator-class there is a static member _thickness that is never assigned to (a compiler warning is shown when building the project), because of that a balloon will never be shown....

Commented Issue: exception in ElementFlow if the itemsSource is not empty at creation [5477]

rumzeus — Wed, 10 Nov 2010 14:01:39 GMT

In FluidKit.Showcase, modify StringCollection with
public StringCollection()
{
Add("/ElementFlow/Images/01.jpg");
Add("/ElementFlow/Images/01.jpg");
Add("/ElementFlow/Images/01.jpg");
}

Then start the elementFlow showcase, and it instantly raises an exception :
'[Unknown]' property does not point to a DependencyObject in path '(0)[0].(1)[1].(2).(3)[0].(4)'.

Sometimes the showcase starts but only one element is displayed and the exception arises when I try to scroll with the mouse.

the exception is raised in LayoutBase::SelectElement line centerSB.Begin
Comments: ** Comment from web user: rumzeus **

with changeset 51117 the following change (in LayoutBase) might help sometimes:
//for (int afterIndex = selectionIndex + 1; afterIndex < Owner.Items.Count; afterIndex++)
for (int afterIndex = selectionIndex + 1; afterIndex < Owner.ContainerCount; afterIndex++)

Created Issue: ElementFlow crashes in remote desktop session [7454]

XjamieX — Thu, 28 Oct 2010 14:05:52 GMT

This may be hard to reproduce as it seems to be related to a graphics card driver. It only happens on a certain machine during remote desktop sessions. If I log in to the machine locally it is not reproducable, also remoting to other pcs it does not occur. We only have 1 machine with this hardware setup so I can't determine for sure if it is a hardware problem or driver related.

Here are my machine specs:
CPU: 2X Intel Xeon X5670
RAM: 24 GB
OS: Windows 2008 R2 64 Enterprise Bit
Graphics Card: ATI Firepro 2260 (latest driver v8.723.0.0)

This first appeared in an application that uses fluid kit, but I can reproduce using the showcase. Steps to reproduce:
- Run FluidKit showcase
- Select 'ElementFlow' in left menu panel
- Click 'Add TypeA' -> crash

If you have the debugger attached already it will crash the vs hosting process. But I can attach after the fault occurs, the exception message is an access violation (see attached screenshot).
Here is the stack trace for what it's worth, shows the fault occurs inside a DirectX9 call:

> d3d9.dll!wmt_CMappingCompiler2::BindMappings() + 0x80 bytes
d3d9.dll!wmt_GlobalInit() + 0x220 bytes
d3d9.dll!SIMD_VMM_WORD::SIMD_VMM_WORD() + 0x1d0 bytes
d3d9.dll!wmt_PVFUNCS::ProcessTriangleFan() + 0x7e bytes
d3d9.dll!wmt_PVFUNCS::ProcessPrimitive() + 0xb3 bytes
d3d9.dll!CD3DDDIDX8::ProcessPrimitiveC() + 0x13b bytes
d3d9.dll!CD3DBase::DrawPrimitive() + 0xa6 bytes
wpfgfx_v0300.dll!CD3DDeviceLevel1::DrawPrimitiveUP() + 0x44b bytes
wpfgfx_v0300.dll!CD3DDeviceLevel1::FlushBufferFan() + 0x30 bytes
wpfgfx_v0300.dll!CD3DDeviceLevel1::RenderTexture() + 0x24b bytes
wpfgfx_v0300.dll!CD3DDeviceLevel1::TestRenderTargetFormat() + 0x351 bytes
wpfgfx_v0300.dll!CD3DDeviceLevel1::CheckRenderTargetFormat() + 0x76 bytes
wpfgfx_v0300.dll!CHw3DSoftwareSurface::Create() + 0x9b bytes
wpfgfx_v0300.dll!CSwRenderTargetSurface::Begin3D() + 0x70 bytes
wpfgfx_v0300.dll!CMetaRenderTarget::Begin3D() + 0xfb bytes
wpfgfx_v0300.dll!CDesktopRenderTarget::Begin3D() + 0x15 bytes
wpfgfx_v0300.dll!CDrawingContext::Begin3D() + 0xd6 bytes
wpfgfx_v0300.dll!CDrawingContext::Render3D() + 0xe0 bytes
wpfgfx_v0300.dll!CMilViewport3DVisual::RenderContent() + 0x50 bytes
wpfgfx_v0300.dll!CDrawingContext::PreSubgraph() + 0x684 bytes
wpfgfx_v0300.dll!CGraphIterator::Walk() + 0x46 bytes
wpfgfx_v0300.dll!CDrawingContext::DrawVisualTree() + 0x42b bytes
wpfgfx_v0300.dll!CDrawingContext::Render() + 0x471 bytes
wpfgfx_v0300.dll!CSlaveHWndRenderTarget::Render() + 0x291 bytes
wpfgfx_v0300.dll!CRenderTargetManager::Render() + 0x4e bytes
wpfgfx_v0300.dll!CComposition::Render() + 0x28 bytes
wpfgfx_v0300.dll!CComposition::ProcessComposition() + 0x10b bytes
wpfgfx_v0300.dll!CComposition::Compose() + 0x52 bytes
wpfgfx_v0300.dll!CPartitionThread::RenderPartition() + 0x28 bytes
wpfgfx_v0300.dll!CPartitionThread::Run() + 0x60 bytes
wpfgfx_v0300.dll!CPartitionThread::ThreadMain() + 0x1c bytes
kernel32.dll!BaseThreadInitThunk() + 0xd bytes
ntdll.dll!RtlUserThreadStart() + 0x21 bytes

Commented Issue: exception in ElementFlow if the itemsSource is not empty at creation [5477]

rumzeus — Mon, 25 Oct 2010 09:02:58 GMT

It seems the problem can be avoided by postponing (by wrapping in Dispatcher.BeginInvoke) these updates in ElementFlow.PrepareModel and ClearModel, respectively:

Dispatcher.BeginInvoke(DispatcherPriority .Normal, new Action (() =>
{
if (IsLoaded)
{
ReflowItems();
}
}));

and

// Update SelectedIndex if needed
Dispatcher.BeginInvoke(DispatcherPriority .Normal, new Action (() =>
{
if (SelectedIndex >= 0 && SelectedIndex < Items.Count)
{
ReflowItems();
}
else
{
SelectedIndex = Math .Max(0, Math .Min(SelectedIndex, Items.Count - 1));
}
}));

Commented Issue: exception in ElementFlow if the itemsSource is not empty at creation [5477]

rumzeus — Wed, 13 Oct 2010 08:09:37 GMT

The ElementControl overrides PrepareContainerForItemOverride and calls PrepareModel to insert a mesh into _modelContainer for each Item.
Later in ElementFlow.BuildTargetPropertyPath (which is called via ElementFlow.SelectItemCore -> LayoutBase.SelectElement -> ElementFlow.PrepareTemplateStoryboard) it is assumed that such a mesh has been inserted into _modelContainer.
This exception occurs when the mesh has not been inserted into _modelContainer. WPF calls PrepareContainerForItemOverride on ApplyTemplate. This is only done once. Items added later are never processed like that.

Commented Issue: System.InvalidCastException [7050]

MCChuwanga — Sun, 10 Oct 2010 01:33:40 GMT

The Designer of VisualStudio generates this Exception when he tries to Convert the System.Windows.NameScope into the System.XAML.NameScope. The Error occurs in Controls\UIFlow3D\UIFlow3D.cs:Line 567 in the procedure
"private void UpdateElementIndexes(UIElement affectedElement, bool attach)", when he does this:

567 NameScope scope =(NameScope) NameScope.GetNameScope(_viewport);
Comments: ** Comment from web user: MCChuwanga **

What worked for me was changing the mentioned line to the following:

INameScope scope = NameScope.GetNameScope(_viewport);

hope that helped.

Commented Issue: ElementFlow does not respect size settings for elements [6256]

rehan — Tue, 24 Aug 2010 08:06:15 GMT

ive tried to set the ElementHeight and ElementWidth - doesnt work, the elements still "stretch" as the container gets larger
ive tried to set explicit heights and widths on the datatemplates for the elements, doesnt work, the elementflow is still dynamically resizing them..
Comments: ** Comment from web user: rehan **

I submitted a patch to add this new feature. Please see the patch section under the source control tab.

Created Issue: System.InvalidCastException [7050]

VisibleBasix — Fri, 30 Jul 2010 15:04:12 GMT

Created Issue: outofMemoryException [6907]

vinayakbaddi — Mon, 28 Jun 2010 13:33:35 GMT

Getting this error on outofmemoryException on ElementFlow.
Could anyone help me. My window is not transparent, its just a plain window calling ElementFlow under it. When Adding Items to ElementFlow it gives me this Intermittent error.
Today it is not ready to go and annoying me.

Commented Issue: ElementFlow does not respect size settings for elements [6256]

ftballguy45 — Mon, 10 May 2010 18:43:19 GMT

hello???

Commented Issue: ElementFlow does not respect size settings for elements [6256]

ftballguy45 — Sun, 04 Apr 2010 03:34:35 GMT

Anyone?

Commented Issue: ElementFlow does not respect size settings for elements [6256]

ftballguy45 — Wed, 31 Mar 2010 14:53:49 GMT

also thanks for the reply :)

Commented Issue: ElementFlow does not respect size settings for elements [6256]

ftballguy45 — Wed, 31 Mar 2010 14:52:52 GMT

Sorry i didnt make myself clear. The problem is I "dont" want the items in the collection to scale up and down as the container of the element flow changes. I want them to stay a consistent size. Lets imagine a series of 50wx50l borders with 6 cornerradius. I want them to stay that size no matter how long the element flow is or how tall it is. Does that make more sense? I bet I am mixing concepts because although experienced with WPF and 2D, Im am raw and new to 3D. I guess I dont really "need" or want the 3D-ness. I took the the ElementFlow and used the SlideDeck layout to give me a nice horizontal scrolling list (imagine in my situation a list of attractive elements that represent a list of video cameras for an application, the user can quickly scrub through the elements with this control using the mouse wheel). Is there a way or a control here that can give me the coolness of the smooth scrolling without the 3Dness and unexpected scaling?

Commented Issue: ElementFlow does not respect size settings for elements [6256]

schungx — Wed, 31 Mar 2010 07:24:39 GMT

Not sure that I understand your question. It seems that you are trying to change the size of individual items. You can't -- each item has a fixed height programmed in. All you can do is to use a container large enough for the largest item, leave its background as transparent, then position your item inside.

If you are trying to change the uniform size of the 3D elements, then you're mixing up concepts. 3D sizing is completely different from 2D sizing. As far as I know, ElementHeight and ElementWidth are only used to: 1) set a resolution for the base images, 2) determine the aspect ratio of the items.

Then the images of the items will be sent to the 3D elements and displayed as stretched. You cannot control the sizing of the 3D elements this way because 3D sizing is a completely different concept.

Since each 3D element has a height of 2 (and width determined by the aspect ratio described above), an indirect method of controlling the 3D element will be to manipulate the camera. Moving it further will make the items smaller, moving it nearer will make the items larger.