|Thank you for the response.
I think the magic number is a fudge factor to allow your workaround to have a little room to see the mouse before the column actually gets to the
MinWidth size. If it finally reaches that size, the column will stop shrinking, but the
Grid starts to grow causing
dWidth to get larger along with
Using binding I ran a test with
GridSplitterEx to watch the size of the right column as the splitter moved right. The column would shrink to a size of about 210 pixels (close to
MinWidth + 12) plus or minus a pixel or two (it wasn't always the same), when the splitter would stop moving.
So your code does workaround the problem for the simplified
Window I presented, giving the approximate minimum size for the column, but it did not work unmodified, if I added another column between the splitter and the last column in my XAML.
The problem is not that the
MinWidth is ignored, but that the right hand columns are being pushed to the right. Even if several columns are given fixed widths on the right of the splitter, as long as there is one column with a
Width of "*" left of the splitter, it will push the right hand columns completely off the window.
Perhaps there is a setting to keep the
Grid from growing beyond the edge of its container. If so, that might prevent this behavior.