9Rays.Net - Forums - .NET - FlyGrid.Net (Windows Forms) - Post#28859 - Invalidating Cells?

Home - Forums-.NET - FlyGrid.Net (Windows Forms) - Invalidating Cells?

FlyGrid.Net (Windows Forms)

.NET Datagrid - Fast, highly customizable, industry standards .NET data grid control for WinForms

This forum related to following products: FlyGrid.Net

Invalidating Cells?

Previous 1 2 3 Next

Link Posted: 06-Feb-2006 07:18

Anonymous

Total Posts:0

Joined:1/7/2025

1. This screenshot shows a newly opened grid. From the hover you can see that the cells actually contains values but they are not displayed unless I click on the cell. Some cells however are invalidated

2. Columns are custom culomns inherited from Column. It shows the same behavior when I comment out overridden PaintTextInCell, etc. code in CustomnColumn. Also it shows the same behavior for standard HierachyColumn like "Strike" column.

3. Add nodes
4. no
5. Well, that's the whole point if I don't call InvalidateNode() the cells don't invalidate. Calling InvalidateCell doesn't work and just setting the cell values doesn't invalidate cells as expected.

Link Posted: 06-Feb-2006 07:22

Anonymous

Total Posts:0

Joined:1/7/2025

Also, the screenshot shows sizing problem that I haven't gotten any response to yet. Last column is too slow compared to the others although all columns are set to AutoSize and FitMode.Spring

Link Posted: 06-Feb-2006 07:23

Anonymous

Total Posts:0

Joined:1/7/2025

I meant too short, not slow, sorry

Link Posted: 06-Feb-2006 07:42

NineRays

Total Posts:0

Joined:1/7/2025

5.Node invalidation code.

Sorry, at this point I meant node contents changing code.

Did you check the column for invalidation
if used node[col] = someValue?
May be incorrect column is used for invalidation?

Link Posted: 06-Feb-2006 08:15

Anonymous

Total Posts:0

Joined:1/7/2025

nope, because if I call InvalidateNode() after node["myColumn"] = value it works correct. But the point is that only very few of the column values change on each quote update so I don't want to waste time invalidating the full node rather than just the cell.

Link Posted: 06-Feb-2006 09:05

Anonymous

Total Posts:0

Joined:1/7/2025

On the image you can see that having to call InvalidateNode here is the major performance problem:

Link Posted: 07-Feb-2006 03:12

Anonymous

Total Posts:0

Joined:1/7/2025

Any thoughts about how to correct this?
The node invalidation is pulling major CPU Performance, as shown above.

When running our application with several sub windows - the CPU is running between 30 -90%...(avg at 50%). We are doing everything we can to bring down the CPU Usage and increase performance, however the biggest issue is the node invalidation.

If anyone can offer a solution or suggestion....we are listening.

Thanks...

Link Posted: 07-Feb-2006 03:24

NineRays

Total Posts:0

Joined:1/7/2025

Currently we're build a sample project to test this problem,
but it is very strange.
Perhaps problem in cell data fetching/translating, please check performance of this task.

Link Posted: 07-Feb-2006 05:26

Anonymous

Total Posts:0

Joined:1/7/2025

I'm not sure what you mean but I posted a performance profile anyways. As you can see, the values are properly set into the cell, however I don't see the changes reflected in the grid unless I call this.InvalidateNode(myNode) after I set all cell values.

Link Posted: 07-Feb-2006 08:31

Anonymous

Total Posts:0

Joined:1/7/2025

[quote="Anonymous"]Also, the screenshot shows sizing problem that I haven't gotten any response to yet. Last column is too slow compared to the others although all columns are set to AutoSize and FitMode.Spring

Also, please don't forget about this post!

Previous 1 2 3 Next