Im using 13.1 controls... I have 2 grids grdMain and grdSupp. Both have layouts dependent on a couple of rules. If rule 1 is invoked then certain cells are edit enabled and background colored yellow. If rule 2 is invoked then no cells are editable and the background color is set to color.empty.
When I reset to force rule 2, [grdSupp.Rows.Refresh(RefreshRow.FireInitializeRow);] fires and InitializeRow for grdSupp gets called. However when I call
[grdMain.Rows.Refresh(RefreshRow.FireInitializeRow);] InitializeRow does NOT fire.
My question is what would inhibit the InitializeRow event from firing?
Hello Jeff,
Thank you for posting in our forum.
One possible reason for some event not firing could be if you have disabled them through UltraGrid’s EventManager. Please let me know if you are working in your application with EventManager in order to control the invokes of event procedures.
Please check also if you are correctly handle the InitializeRow event of your main grid.
If you are handle correctly the InitializeRow event and in the same time you are not working with EventManager I will need a small sample solution reproducing this behavior in order to be able to investigate this further.
Please let me know if this information helps you to solve your issue.
Looking forward to your reply.
I don't use EventManager. However I did figure out what the problem is:
RefreshRow.FireInitializeRow is affected by whether or not Group By is turned on. When I turn Group By off then my break point gets hit when I do [grdMain.Rows.Refresh(RefreshRow.FireInitializeRow);] So I think this is a bug with the 13.1 ultragrid. Oh and my grdSupp does NOT use group by... that's the difference between the 2 grids.
I don't think I need to create a test sample project, but you can. My next question is: is there a work around? I would like to have my group by layout and not have to reload the grid with data just to get the InitializeRow to fire. :(
thanks