Unexpected Behavior

[sethrothman]

Hi Joel,

First off, your library has been my "go to" for years so I'll start by expressing my gratitude. And then I'll apologize for this lengthy post...

Here's my situation. I use the DevExpress suite of components when building WinForms apps. In particular, their Grid control exhibits weird behavior when bound to an AsTrackable() collection - but only when using a more current version of Castle.Core (v5+). I opened a support ticket with DevExpress and they helped troubleshoot and narrow the scope of the issue.

Their grid has a property called "ImmediateUpdateRowPosition" which determines whether or not an edited column's sorting/grouping is applied once the field (not row) is committed. I always turn this setting to False because the result is disconcerting otherwise IMHO. In other words, if you have a grid that's grouped, changing the value of the grouped field will automatically move the row to its "new" grouped location which means you can't edit the remaining fields in the row first. I attached a small video showing the undesired behavior.

Anyway, the issue is that the ImmediateUpdateRowPosition property is basically ignored in the scenario I described above. If I revert to v4 of Castle.Core, everything works as expected. Any thoughts on why the behavior changed? I generally try to keep current with 3rd party nuget packages and Castle.Core is the one standout I'm unable to upgrade.

2023-07-12_05-51-48.mp4

FYI, I attached the small sample I was working with DevExpress on in case you wanted to see it in action. It'd require you install a trial of the DevEx components unfortunately.

T1177040.zip

If you have any thoughts, I'd love to hear them. Thx.

[barmendarez]

We also have had unexpected behavior with this library. There is something breaking with the the latest Castle.Core (EF Core uses the latest version so we had to update)

[joelweiss]

This library is not compatible with Castle.Core v5 due to #647, the issue you are experiencing might be related.

Unfortunately I have not had the time (yet) to come up with a fix.

[sethrothman]

Thanks for the follow-up Joel. On Tuesday, October 8, 2024 at 01:35:08 PM EDT, Joel Weiss ***@***.***> wrote: This library is not compatible with Castle.Core v5 due to #647, the issue you are experiencing might be related. Unfortunately I have not had the time (yet) to come up with a fix. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>