Hi there,
We have just upgraded from SL4 to SL5, and since this, the XamDialogWindow behaviour has been differnent.
All errors revolve around error 2028 ( Message: The name already exists in the tree )
1: When opening a Dialog Window, and closing it with the X control instead of a Cancel button, and re-opening another Dialog window of the same type, the error is thrown.
2: When a Dialog Window is responsible for opening a second Dialog Window, this error is thrown.
Can you offer any advice on working around these situations? We are using SL5 with Infragistics 2012.1
thanks,
Matt.
We have implemented a workaround for scenario 1, where in a behaviour, the WindowStateChanged is overriden to actually close the dialog instead of hide it, but any suggestions for Number 2 would be most appreciated still.
Hello Matt,
Thank you for your post I have been looking into it and I created a sample project for you following your scenario and everything seems to work ok on my side. I tested the sample with both the RTM(1016) and latest service release(2206) of 12.1. If the sample doesn’t satisfies all your needs feel free to modify it, so it reproduces your behavior and send it back to me for further investigation.
Looking forward for your reply.
Thanks for the reply,
We found another workaround for this, as it appeared that the error was not just to do with the x:Name of the DialogWindow being present in the visual tree, but the controls we used also.
Our approach was pretty generic, and all ok buttons were called x:Name="OkControl" and all cancel buttons x:Name="CancelControl", so as more panels were created, these were clashing. So all we need to do is change our naming convention so that these controls have unique names across panels.
Hopefully MS will fix this in a future SL patch!
Thank you for your feedback. I am glad that you resolved your issue and I believe that other community members may benefit from this as well.
Thanks again.